Alex Thorn weist auf Bitcoin-Block (BTC) mit Zeitstempel drei Minuten vor seinem Vorgänger hin

Crypto News and Tradfi News - COINOTAG · 2026-11-08T17:49:53.000Z

• Block 974,988 erhielt am 7. November den Zeitstempel 21:19:02 UTC – mehr als drei Minuten vor seinem Vorgängerblock 974,987. • Alex Thorn zufolge tragen etwa 3 % der Bitcoin-Blöcke einen früheren Zeitstempel als ihre Vorgängerblöcke. • Etwa jeder zehnte Bitcoin-Block kommt mit einem Zeitstempel an, der mehr als eine Minute vor dem Empfangszeitpunkt des Knotens liegt. Block 974,988 lässt seine Uhr rückwärts laufen Bitcoin (BTC) sorgte am Samstag, dem 7. November, kurzzeitig für Aufregung in seinem Netzwerk: Miner erzeugten einen Block, dessen Zeitstempel vor dem des Blocks lag, an den er anknüpfte – ein scheinbarer Bruch der Chronologie in einem Ledger, das auf verlässliche Reihenfolge ausgelegt ist. Block 974,987 trug den Zeitstempel 21:22:24 UTC. Block 974,988, der danach geschürft wurde, hatte den Zeitstempel 21:19:02 UTC. Im öffentlichen Block-Explorer lag der neuere Block damit mehr als drei Minuten hinter seinem eigenen Vorgänger. Beide Einträge befanden sich auf derselben Chain, direkt hintereinander. Es kam also weder zu einer Abzweigung noch zu einer Umkehrung; die Blockchain verzeichnete lediglich eine Uhrzeit in der falschen Reihenfolge. Innerhalb einer Stunde machten die Fragen im Bitcoin-Netzwerk und in dessen Beobachtergemeinschaft die Runde. Alex Thorn, Forschungsleiter bei Galaxy Digital, wies binnen weniger Minuten auf die Abfolge hin. Der Explorer zeige Block 974,988 als 22 Minuten alt an, während sein Vorgänger mit 18 Minuten angegeben werde; auch sein eigenes Dashboard weise dieselbe Abweichung auf. Keine der beiden Anzeigen sei falsch, schrieb er, denn den Zeitstempel eines Blocks legt der Miner fest, der ihn schürft – nicht das Netzwerk, das ihn validiert. Bei der Suche nach einem gültigen Hash passen Miner dieses Feld an und erzeugen zusätzliche Kombinationen, die ihre Geräte testen können. Außerdem stellen sie die Uhr vor, um neue Arbeit zu erhalten. Deshalb liegen die Zeitstempel im gesamten Netzwerk meist etwas vor der tatsächlichen Uhrzeit. Der Konsens legt die Regeln für dieses Feld ohnehin großzügig aus: Der Zeitstempel eines Blocks muss lediglich nach der Medianzeit der elf vorherigen Blöcke liegen und darf der Uhr des validierenden Knotens höchstens zwei Stunden voraus sein. Die Zwei-Stunden-Grenze verhindert extrem weit in der Zukunft liegende Zeitstempel, während die Medianprüfung sicherstellt, dass kein einzelner Miner die gemeinsame Uhr des Netzwerks verschieben kann. Die Regeln verlangen nicht, dass ein Block einen späteren Zeitstempel hat als der vorherige. Die Kursdaten und Abwicklungen von Bitcoin (BTC) liefen währenddessen ohne Unterbrechung weiter.

• Block 974,988 was stamped 21:19:02 UTC on November 7, more than three minutes behind parent 974,987.
• Alex Thorn says about 3% of Bitcoin blocks carry timestamps earlier than their parents.
• About one in ten Bitcoin blocks arrives stamped more than a minute ahead of node receipt.
Block 974,988 Runs Its Clock Backward
Bitcoin (BTC) gave its network a brief scare on Saturday, November 7, when miners produced a block whose timestamp predated the block it extended, an apparent break in chronology on a ledger built for ordered certainty. Block 974,987 was stamped 21:22:24 UTC. Block 974,988, mined afterward, carried a timestamp of 21:19:02 UTC, which placed the newer block more than three minutes behind its own parent on the public block explorer. Both entries sat on the same chain, one directly after the other, so nothing forked and nothing was reversed; the blockchain simply recorded an out-of-order clock. Questions spread across the Bitcoin network and its observer community within the hour. Galaxy Digital's head of research, Alex Thorn, flagged the sequence in minutes, noting that the explorer showed block 974,988 as 22 minutes old while its parent showed 18, and that his own dashboard displayed the same gap. Neither display was wrong, he wrote, because the timestamp inside a block is set by whoever performs the mining, not by the network that validates it. Miners adjust that field while searching for a valid hash, generating additional combinations for their machines to test and rolling the clock forward to receive fresh work, which is why stamps across the fleet tend to sit slightly ahead of wall-clock time. Consensus treats the field loosely in any case: a block's stamp only has to beat the median time of the previous eleven blocks, and it cannot run more than two hours ahead of the validating node's clock. The two-hour ceiling fences off extreme forward stamps, while the median test keeps any single miner from dragging the network's shared clock. Nothing in the rules requires a block to be later than the one before it. Bitcoin (BTC) price feeds and settlement ran through the sequence without interruption.
The deeper question is whether a backward clock threatens settlement, and the record says no. Order on the chain is fixed by cryptographic links, not by timestamps: every block carries the unique hash of the block before it, which settles which came first. A genuine reorganization would require a competing chain carrying more accumulated work than the current one, and no amount of timestamp editing produces that. Thorn's follow-up put numbers on how often clocks drift: roughly 3% of all Bitcoin blocks carry timestamps earlier than their parents, and about one in ten arrives stamped more than a minute ahead of the moment his node received it. Saturday's three-minute gap is an outlier in size, not in kind. The design accepts a loose clock because sequence, not time, is what the ledger guarantees. Satoshi Nakamoto described the system as a “timestamp server” in the original whitepaper, and eighteen years on the description holds: the network proves order cryptographically and treats its own clock as approximate. That is a deliberate contrast with a blockchain oracle, which moves external data on-chain on the strength of the feed, while Bitcoin builds approximation into its own time field by construction. For a layer 1 protocol, the distinction separates two different guarantees: what came first, and roughly when. The median-of-eleven test draws on a rolling window, so one skewed stamp bends the shared clock only slightly, and the forward ceiling removes the remaining extremes. Miners who want the earliest start on the next round roll their stamps toward the front of the allowed window, which is the mechanical reason drift accumulates. Thorn's statistics frame the surprise: with roughly three inverted parents in every hundred blocks, a chain that always ticked in order would itself be the anomaly.
What the Timestamp Skew Means Off-Chain
For anyone keeping records off the chain, the practical read is narrower than the alarm suggests. With roughly 3% of blocks stamped behind their parents and one in ten running a minute ahead of node receipt, a timestamp dates an event only approximately, while block height fixes sequence exactly. Reporting that quotes block times as precise moments, from deposit logs to settlement reconciliations, inherits that slack. The variance also fits the lottery character of block production, in which two solo miners won $476,000 blocks hours apart on CKPool. Saturday's episode changed nothing about consensus: it was visible, explained and absorbed within the same day, with the chain's ordering rules doing exactly the job they were written to do.