Transactions very slow tonight

[calkob]

i sent a lot of transactions earlyer and some are still waiting there 1st confirmation after an hour.  anyone any ideas why?

[1714814472]

1714814472

[1714814472]

1714814472

[1714814472]

1714814472

[1714814472]

1714814472

[1714814472]

1714814472

[1714814472]

1714814472

[shorena]

i sent a lot of transactions earlyer and some are still waiting there 1st confirmation after an hour.  anyone any ideas why?

If you post your transaction ID we probably can tell you more. Without any more information I can only give you a generic there are currently many transactions waiting for a confirmation.



see also -> http://statoshi.info/dashboard/db/transactions

[calkob]

Thanks shorena, dont think its a problem.  was just wondering what if anything was slowing down transactions tonight.  paid a 0.0003 fee on the longest one too.

[emelac]

Thanks shorena, dont think its a problem.  was just wondering what if anything was slowing down transactions tonight.  paid a 0.0003 fee on the longest one too.

The last six blocks don't have any huge time delays between them, but they are all close to full. Your problem is probably caused by a queue of transactions waiting to be included in a block, with your transactions at the back of the queue. The last block wasn't full so your wait might be over soon.

Height   Age   Transactions   Total Sent   Relayed By   Size (kB)
384066   11 minutes   2241   14,474.98 BTC   AntPool   731.5
384065   22 minutes   202   20,923.64 BTC   BTCC Pool   926.89
384064   44 minutes   1599   12,793.41 BTC   AntPool   912.37
384063   51 minutes   1908   13,796.23 BTC   AntPool   911.33
384062   1 hour 3 minutes   1986   21,479.33 BTC   BW.COM   926.82
384061   1 hour 16 minutes   2697

[mirana12345]

i sent a lot of transactions earlyer and some are still waiting there 1st confirmation after an hour.  anyone any ideas why?

It's because they're waiting in queue to get confirmed. You may have paid a fair fee, but there's still transactions that had higher priority or were before yours, so you just have to
wait for them to get confirmed fist.
Also, if you send transaction from multiple inputs, you may want to pay fee in relation to kb, and not the amount of funds sent.

[MRKLYE]

i sent a lot of transactions earlyer and some are still waiting there 1st confirmation after an hour.  anyone any ideas why?

It's because they're waiting in queue to get confirmed. You may have paid a fair fee, but there's still transactions that had higher priority or were before yours, so you just have to
wait for them to get confirmed fist.
Also, if you send transaction from multiple inputs, you may want to pay fee in relation to kb, and not the amount of funds sent.

+1 to this advice. Often when. You send from multiple inputs or addresses it is wide to include a txfee of around .0003 BTC or more just so the miners are more likely to grab the transaction and include it in their block. It's alot of work to hash large transactions with many inputs in to blocks and the mining programs know this and tend to leave low fee paying transactions till they run out of work.

[calkob]

cheers i'm starting to learn abit here (which is always good).  is it because of the many inputs?  many thanks to all who replied .Here's the receiving address to check it out

 1Asmy7k2DKj4i4pMqc8jQDr7pqDydzVboj

[Carlton Banks]

cheers i'm starting to learn abit here (which is always good).  is it because of the many inputs?  many thanks to all who replied .Here's the receiving address to check it out

 1Asmy7k2DKj4i4pMqc8jQDr7pqDydzVboj

Likely yes. Transaction fees are considered on a BTC/kB basis. One input is minimum 226 bytes, not sure how much is added per additional input (possibly not as much as 226 bytes though)

[shorena]

cheers i'm starting to learn abit here (which is always good).  is it because of the many inputs?  many thanks to all who replied .Here's the receiving address to check it out

 1Asmy7k2DKj4i4pMqc8jQDr7pqDydzVboj

-> https://www.blocktrail.com/BTC/tx/bff075f41361d1d56697cc956208b1c64c69e6180e3624683c7faab5b51b4652

2410 bytes, 30k satoshi fee boils down to ~12.45k satoshi per kbyte which is according to bitcoin core pretty high.

You dont create any dust outputs, all inputs are confirmed, etc. should only take a couple of blocks.

-snip-
Likely yes. Transaction fees are considered on a BTC/kB basis. One input is minimum 226 bytes, not sure how much is added per additional input (possibly not as much as 226 bytes though)

IIRC rule of thumb is 180 byte per input, 34 byte per output and a few bytes (10?) on top of that.

[tom555]

post your transaction ID dude,and maybe we can check it out,and tell you something about a pending transaction,i think many people can explain about this matter..and i hope its has been solved,because i also ever have a same problem,when i am hurry up,i must wait a fu*king slow transaction,it been long time or several hour,and confirmation still one,and it happen on many exchange or wallet,i also have a not good experience with some wallet,include a coinbase

[gogxmagog]

I think most of us are prepared for long confirmation times (possibly) and can use block explorer to watch them go through, but honestly, this has been at issue for years. If I use cc or interac I get instant payment. I'd like to see btc move a lot faster. That's why I support increased block size.

[justbitcoins]

The transaction is quite slow tonight. I paid 5111 satosh/kb, which is the default setting of Core wallet.  I have waited for more than 1 hours 20 mins, still no confirmation.

[Lauda]

The transaction is quite slow tonight. I paid 5111 satosh/kb, which is the default setting of Core wallet.  I have waited for more than 1 hours 20 mins, still no confirmation.

What did you expect when you have people like me who tend to pay 0.01 BTC as a fee or higher? Using the default setting will only make your transactions get thrown in the same bucket as the transactions of a lot of other people that use the same setting. The higher you go (fee wise) the less people there will be before you.

[calkob]

heres the hash.  thanks again all....


bff075f41361d1d56697cc956208b1c64c69e6180e3624683c7faab5b51b4652