Bitcoin's blockchain recorded a block with a timestamp earlier than its predecessor on November 7. Block 974,988 showed a timestamp of 21:19:02 UTC, while the prior block 974,987 displayed 21:22:24 UTC, making the newer block appear three minutes older.
Alex Thorn, Galaxy Digital's research head, explained the mechanics behind the anomaly. Miners set the timestamp for each block and can adjust it while searching for a valid block. Bitcoin's consensus rules permit this flexibility under two constraints: a timestamp must exceed the median time of the previous 11 blocks, and it cannot exceed two hours ahead of a validating node's clock. Critically, the rules do not require a timestamp to be later than the immediately preceding block.
Thorn's analysis found that 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.
The backward timestamp does not threaten transaction security or block order. Bitcoin establishes sequence through cryptographic links, not timestamps. Each block contains the previous block's unique hash, determining which came first. A genuine blockchain reorganization requires a competing chain with more accumulated mining work. Changing timestamps cannot achieve that.
For anyone relying on blockchain records to establish when an event occurred, the distinction matters. Bitcoin's block height establishes sequence. Its timestamp provides an approximate time. Satoshi Nakamoto described Bitcoin as a "timestamp server" in the original whitepaper. The November 7 incident shows why that system relies on cryptographic proof rather than a perfectly accurate clock.