Bitcoin Forum

Bitcoin => Bitcoin Discussion => Topic started by: atlosas on March 11, 2015, 03:38:09 PM



Title: Longest and shortest block time
Post by: atlosas on March 11, 2015, 03:38:09 PM
Hi, what was the longest and shortest time between blocks in bitcoin history?


Title: Re: Longest and shortest block time
Post by: juju on March 11, 2015, 05:56:27 PM
Hi, what was the longest and shortest time between blocks in bitcoin history?

This question has been asked a few times in the past, some quick google searching found:

http://bitcoin.stackexchange.com/questions/2324/what-is-the-longest-time-gap-between-blocks-in-2010-2011

Quote
I wrote a program that extracts the blockchain into an SQL database and ran a query. The answer is that block 152218 followed block 152217 after a delay of 1 hour 39 minutes 7 seconds. This was the longest inter-block interval in 2011. There were many longer interval in the early history of the blockchain, often multiple hours or days.

Edit: I also find it interesting that there have been 78 blocks where the inter-arrival time was less than one second.

I recall answering a similar question regarding waiting for confirmations:
https://bitcointalk.org/index.php?topic=954942.msg10452529#msg10452529


Title: Re: Longest and shortest block time
Post by: belmonty on March 11, 2015, 09:30:10 PM
http://www.reddit.com/r/Bitcoin/comments/1vkp1x/what_is_the_longest_time_between_blocks_in_the/

Much larger time gaps earlier on.

Block 27: 2009-01-10 06:56:13
Block 28: 2009-01-10 15:30:57
Block 168: 2009-01-11 23:39:41
Block 169: 2009-01-12 03:22:03
Block 74637: 2010-08-15 17:02:43
Block 74638: 2010-08-15 23:53:59

Block 0 was mined 128 hours, 39 minutes and twenty seconds before Block 1.


Title: Re: Longest and shortest block time
Post by: rikkie on March 15, 2015, 02:10:48 AM
I have no idea as to the accuracy to the above answers, however I have seen multiple times two blocks being found almost one right after the other, sometimes by the same pool.

Also it is very difficult to answer this question because the time stamp on the node that broadcast the block initially could be off by up to two hours. As a result I would say the shortest block interval would be only seconds.

I do not know about the longest block interval, but I do know that it exceeds several hours


Title: Re: Longest and shortest block time
Post by: bensam123 on March 15, 2015, 04:23:43 AM
The shortest, I've seen 2-3 blocks go by at the same time.

While the longest and the most miserable I've seen was I was trying to send BTC0.5, and there wasn't a single block for about 6 hours. That's probably not the longest though.


Title: Re: Longest and shortest block time
Post by: jwcastle on March 15, 2015, 04:41:16 AM
Just from personal experience, I was in a pool that mined consecutive blocks within about 20 seconds. That was a good day! Just lucky.

I'm sure the shortest ever in history is probably one second or less.


Title: Re: Longest and shortest block time
Post by: sakira on March 15, 2015, 11:45:54 AM
just from my personal experience, the fastest confirmation about 40 seconds and the longest 3 days :)


Title: Re: Longest and shortest block time
Post by: randy8777 on March 15, 2015, 12:02:04 PM
just from my personal experience, the fastest confirmation about 40 seconds and the longest 3 days :)

3 days waiting isn't exactly worth saving 0.0001btc right? or did you forget to add a fee.
to avoid this you can in most wallets clients set a minimum fee. so it won't happen again.


Title: Re: Longest and shortest block time
Post by: sakira on March 15, 2015, 11:47:57 PM
just from my personal experience, the fastest confirmation about 40 seconds and the longest 3 days :)

3 days waiting isn't exactly worth saving 0.0001btc right? or did you forget to add a fee.
to avoid this you can in most wallets clients set a minimum fee. so it won't happen again.

haha yeah right, I forgot to put the fee :D, first I want to try it, it turns out it was very long, and almost the rest of my balance could not be sent because they have to wait for the transaction is confirmed.

yes now I always put the cost of recommendation so that does not happen again :D