A newly mined Bitcoin block appeared to run backward in time on November 7, showing an earlier timestamp than the block that preceded it. The discrepancy raised an unusual question about whether the Bitcoin blockchain had developed a bug.
Galaxy Digital research head Alex Thorn highlighted the incident and explained why Bitcoin's internal clock does not always follow real-world time.
Two consecutive blocks
The sequence involved two consecutive blocks:
- Block 974,987 was timestamped 21:22:24 UTC.
- Block 974,988 was mined afterward but timestamped 21:19:02 UTC.
According to Bitcoin's public blockchain explorer, the newer block appeared more than three minutes older than its predecessor.
Why the clock can run backward
The explanation lies in how Bitcoin mining works. Miners choose the timestamp attached to each block and can adjust it while searching for a valid block, creating additional combinations for their computers to test.
Bitcoin permits this flexibility under two rules: a timestamp must exceed the median time of the previous 11 blocks, and it cannot be more than two hours ahead of a validating node's clock. Crucially, the timestamp does not have to be later than the immediately preceding block.
According to Thorn's analysis, roughly 3% of Bitcoin blocks carry timestamps earlier than their parents. About one in ten arrives with a timestamp more than a minute ahead of when his node received it.
Thorn noted that consensus checks only that the stamp beats the median of the previous 11 blocks and sits under two hours ahead of the node's clock. Nothing requires a block to be later than the one before it, and miners roll the time forward to get fresh work, so stamps can drift ahead.
Transaction order is unaffected
The timestamp anomaly does not mean Bitcoin transactions can be reversed. Bitcoin determines block order through cryptographic links rather than timestamps. Every block contains the previous block's unique hash, establishing exactly which came first.
A genuine blockchain reorganization requires a competing chain with more accumulated mining work. Changing timestamps cannot achieve that.
The distinction still matters for anyone relying on blockchain records to establish precisely when an event occurred. Bitcoin's block height establishes sequence, while its timestamp provides an approximate time.
Satoshi Nakamoto described Bitcoin as a "timestamp server" in the original whitepaper. The November 7 incident illustrates why that system relies on cryptographic proof rather than a perfectly accurate clock.
