7 hours to confirm?!?! | Bitcointalksearch.org

spiz0r

sr. member

Activity: 340

Merit: 250

Quote from: Jet Cash on May 31, 2016, 06:31:28 AM

Quote from: spiz0r on May 31, 2016, 12:56:32 AM

Quote from: donkeyramp on May 27, 2016, 04:40:51 PM

Can someone explain to me why on earth a small chunk of BTC would take 7 hours for confirmations? I've never seen one take even 2 hours let alone 7... And it was for a small chunk, very small chunk, like .00007 BTC. Just frustrating AF, but I'm curious to know if there's a certain reason why this would happen? Thanks

Usually a transaction like that would arrive fast. But because the 1 mb block size limit we have a lot of delays in transactions at busy days.
I am not sure about the exact time of the transaction but on 27th May the bitcoin network was very overloaded. The mempool was 15 mb, it means that 15 blocks needed to process all of the transactions in the mempool.

You can check it here:
http://bitcointicker.co/networkstats/

You can't blame it solely on blocksize. Throughput is based on vehicle size times the number of vehicles per hour. Increasing the number of vehicles provides a far better solution that creating lumbering giants.

I was just refering to the current situation, with 1 mb blocks and 10 minutes blocktime the network sometimes stuck.
So do you think a reduced (for example 1 or 2 minutes) blocktime would be the solution for the network problems?

DannyHamilton

legendary

Activity: 3472

Merit: 4801

Quote from: Jet Cash on May 31, 2016, 06:31:28 AM

You can't blame it solely on blocksize. Throughput is based on vehicle size times the number of vehicles per hour. Increasing the number of vehicles provides a far better solution that creating lumbering giants.

Your analogy doesn't work in real life or in bitcoin.

Increasing the average size of vehicle (as long as that vehicle is nearly fully loaded) is significantly more efficient and a better solution than increasing the number of vehicles on the road. Buses, trains, and airplanes (when nearly fully loaded) are far more efficient and create far less congestion, collisions, and parking problems than an equal carrying capacity of small vehicles.

Increasing the average size of bitcoin block is more efficient and a better solution than increasing the number of blocks in the blockchain. Larger blocks contain more transactions per kilobyte of blockchain, and have less orphaned blocks, than the same number of transactions spread across more blocks in the same amount of time.

Jet Cash

legendary

Activity: 2814

Merit: 2472

https://JetCash.com

Quote from: spiz0r on May 31, 2016, 12:56:32 AM

Quote from: donkeyramp on May 27, 2016, 04:40:51 PM

Can someone explain to me why on earth a small chunk of BTC would take 7 hours for confirmations? I've never seen one take even 2 hours let alone 7... And it was for a small chunk, very small chunk, like .00007 BTC. Just frustrating AF, but I'm curious to know if there's a certain reason why this would happen? Thanks

Usually a transaction like that would arrive fast. But because the 1 mb block size limit we have a lot of delays in transactions at busy days.
I am not sure about the exact time of the transaction but on 27th May the bitcoin network was very overloaded. The mempool was 15 mb, it means that 15 blocks needed to process all of the transactions in the mempool.

You can check it here:
http://bitcointicker.co/networkstats/

You can't blame it solely on blocksize. Throughput is based on vehicle size times the number of vehicles per hour. Increasing the number of vehicles provides a far better solution that creating lumbering giants.

spiz0r

sr. member

Activity: 340

Merit: 250

Quote from: donkeyramp on May 27, 2016, 04:40:51 PM

Can someone explain to me why on earth a small chunk of BTC would take 7 hours for confirmations? I've never seen one take even 2 hours let alone 7... And it was for a small chunk, very small chunk, like .00007 BTC. Just frustrating AF, but I'm curious to know if there's a certain reason why this would happen? Thanks

Usually a transaction like that would arrive fast. But because the 1 mb block size limit we have a lot of delays in transactions at busy days.
I am not sure about the exact time of the transaction but on 27th May the bitcoin network was very overloaded. The mempool was 15 mb, it means that 15 blocks needed to process all of the transactions in the mempool.

You can check it here:
http://bitcointicker.co/networkstats/

xhomerx10

legendary

Activity: 3808

Merit: 7912

Quote from: donkeyramp on May 27, 2016, 04:40:51 PM

Can someone explain to me why on earth a small chunk of BTC would take 7 hours for confirmations? I've never seen one take even 2 hours let alone 7... And it was for a small chunk, very small chunk, like .00007 BTC. Just frustrating AF, but I'm curious to know if there's a certain reason why this would happen? Thanks

Quote from: donkeyramp on May 27, 2016, 11:46:21 PM

I'm curious enough I guess. Thanks for the response. Here's the ID

92fdf1a3bc4a9e088e5bdb486f571a300be46f488f2402490a15968cda3d3775

It looks like the transaction fee paid per kilobyte was 0.0001 BTC which would cause a delay of anywhere from 2-14 blocks before confirmation. Presently, in order to get a transaction included in the next block, a fee of 0.0005 BTC per kilobyte is required. In all fairness, that transaction was a monster at 20 kb! A higher fee was required. You should complain to the individual who sent you the 4 cents.

Now can you explain to me what is so frustrating about waiting for 4 cents? What were you planning to do buy an ice cream parlor?!

donkeyramp

newbie

Activity: 39

Merit: 0

I'm curious enough I guess. Thanks for the response. Here's the ID

92fdf1a3bc4a9e088e5bdb486f571a300be46f488f2402490a15968cda3d3775

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Usually it is due to a very low fee or that some inputs the transaction depends on are also not yet confirmed. Another is that it could be producing a dust output. The amount transferred usually does not matter (it does in the case of dust outputs, but even transactions with dust outputs will still be confirmed after a slight delay), the actual size in bytes of the transaction does.

If you post the transaction id, we may be able to help you.

donkeyramp

newbie

Activity: 39

Merit: 0

Can someone explain to me why on earth a small chunk of BTC would take 7 hours for confirmations? I've never seen one take even 2 hours let alone 7... And it was for a small chunk, very small chunk, like .00007 BTC. Just frustrating AF, but I'm curious to know if there's a certain reason why this would happen? Thanks

Topic: 7 hours to confirm?!?! (Read 939 times)