Bitcoin appeared to break one of the most basic rules of time on November 7. A newly mined block showed an earlier timestamp than the block before it.
The discovery raised an unusual question: is there a bug in the Bitcoin blockchain?
Galaxy Digital research head Alex Thorn highlighted the incident, explaining why Bitcoin’s internal clock does not always follow real-world time.
Two consecutive blocks told the story.
Block 974,987: Timestamped 21:22:24 UTC.
Block 974,988: Mined afterward, but timestamped 21:19:02 UTC.
The newer block appeared more than three minutes older, according to Bitcoin’s public blockchain explorer .
why does block 974,988 show “22 minutes ago” while the block before it, 974,987, shows 18? mempool dot space and my own dashboard both show it, and neither is wrong. the timestamp inside a block is set by the miner, not by the network pic.twitter.com/sugtYJNyeP
— Alex Thorn (@intangiblecoins) November 7, 2026
Why Can Bitcoin’s Clock Run Backward?
The explanation lies in how Bitcoin mining works.
Miners choose the timestamp attached to each block. They can adjust it while searching for a valid block, creating additional combinations for their computers to test.
Bitcoin allows this flexibility under two rules:
A timestamp must exceed the median time of the previous 11 blocks.
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.
consensus checks two things: the stamp must beat the median of the previous 11 blocks and sit under 2 hours ahead of the node’s clock. nothing actually says a block must be later than the one before it. miners also roll the time forward to get fresh work, so stamps drift ahead
— Alex Thorn (@intangiblecoins) November 7, 2026
Does This Mean Bitcoin Transactions Can Be Reversed?
No. 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.
However, the distinction matters for anyone relying on blockchain records to establish precisely when an event occurred.
Bitcoin’s block height establishes sequence. Its timestamp provides an approximate time.
Satoshi Nakamoto described Bitcoin as a “timestamp server” in the original whitepaper . Eighteen years later, the November 7 incident shows why that system relies on cryptographic proof rather than a perfectly accurate clock.
The post Bitcoin’s Blockchain Just Ran Backward in Time. Is Something Wrong? appeared first on BeInCrypto .
