The chance of a block not being found within a specific time frame is given by the equation:
e(-x/600)
Where x is equal to the number of seconds. If we make x = 3600 for 1 hour, then the chance of a block not being found in 1 hour works out to just under 0.25%. Given that, we would expect to see a 1 hour or more block time every 400 blocks on average, or little bit more frequently than once every 3 days.
This of course assumes that the difficulty and hashrate are constant. If the hashrate has fallen since the last difficulty readjustment, then the chances of longer block times increases.
Topic: 66 minutes between blocks? - page 2. (Read 330 times)
According to blockchain.info, block 699509 was timestamped 17:00 UTC and 699510 was timestamped 18:06 UTC -- a 66-minute interval.
Also, please note that the timestamp is not the actual time. Changing the timestamp is another way to vary the block hash. The timestamp must be later than the median of the last eleven blocks (roughly in the last hour) and not more than two hours greater than the actual time.
If so, what might have been the cause?
Finding the next block is like a random game of chance or probability. In Simple terms, it's like if you are six players (miners) playing a die game and the first person to roll the dice to number 6 wins the game (Mine a new block)You will find a situation where players will take so long to roll a number six after very many attempts, while at other times it will take any of them just seconds to roll a six.
It is why it is called an AVERAGE block time. It would be impossible to set an exact time of 10 minutes per block because there is something miners have to solve and it may take more or less time depending on a few factors such as hashrate or difficulty. If I gave you a math problem, it would be impossible in the same way to make you solve it in exactly 10 minutes. The average time however is 10 min and you find out it is as soon as you start using Bitcoin often.
My transactions typically get one confirmation in at least 5 minutes and at most 15, but it is usually around 10 that it happens. Should the hashrate increase or decrease substantially before the difficulty adjustment, block times change together with it.
-
Regards,
PrivacyG
My transactions typically get one confirmation in at least 5 minutes and at most 15, but it is usually around 10 that it happens. Should the hashrate increase or decrease substantially before the difficulty adjustment, block times change together with it.
-
Regards,
PrivacyG
this is a usual situation that can happen depending on the miners/pools, the longest block time that ever happened is 5 days and 8 hours from the block 1
the 3 longest blocks time from this year are :
block 689301 02h19m
block 679786 02h02m
block 687143 01h59m
the 3 longest blocks time from this year are :
block 689301 02h19m
block 679786 02h02m
block 687143 01h59m
The "10 minute" blocktime is the average interval between blocks which is managed by the mining difficulty, adjusted every two weeks (approximately) to keep the interval uniform.
It can be shorter than that or longer than that depending upon how fast the next cryptographic puzzle is solved.
It can be shorter than that or longer than that depending upon how fast the next cryptographic puzzle is solved.
It didn't happen for a hash to be found with the given conditions. I wouldn't say it's unusual; there's a 10 minutes interval on average between the blocks, but they may take much more than expected. They can also be found in much less time than expected. For example, block 699511 was found 3 minutes right after the previous one.
El Salvador doesn't have to do with this.
El Salvador doesn't have to do with this.
Today is "El Salvador day," so there's lots of news and lots of trading.
According to blockchain.info, block 699509 was timestamped 17:00 UTC and 699510 was timestamped 18:06 UTC -- a 66-minute interval. Isn't that quite unusual? If so, what might have been the cause?
According to blockchain.info, block 699509 was timestamped 17:00 UTC and 699510 was timestamped 18:06 UTC -- a 66-minute interval. Isn't that quite unusual? If so, what might have been the cause?
Jump to: