Bitcoin saw a single-block reorganization on September 11 at block height 966500 after mining pools Spiderpool and Antpool found competing valid blocks referencing the same parent block, with Antpool’s block ultimately kept on the main chain and Spiderpool’s block discarded.

The event began when Spiderpool and Antpool each discovered a valid Bitcoin block that pointed to the same parent. That created a brief fork in which two competing versions of the chain existed at the same height. Bitcoin nodes then continued building on the branch with higher cumulative work, and Antpool’s block was the one that remained in the accepted chain.

The Spiderpool block was discarded as the network resolved the competition. The report did not describe the event as an attack, outage, or software failure. Instead, it presented the reorganization as a consensus-level outcome of simultaneous block discovery, a known edge case in proof-of-work networks.

The report also said this was the third single-block reorganization on Bitcoin in the past four weeks, following earlier cases at block heights 962722 and 963853. No further details were provided for those two incidents, including the pools involved or whether they produced any material operational disruption.

Bitcoin has seen similar episodes before. In a separate earlier case at block height 941880, the network experienced a two-block reorganization in which competing branches briefly emerged before one chain was retained and the other blocks were orphaned. That case was also described as a normal result of Bitcoin’s decentralized consensus process rather than a sign of a broader network failure.

Why It Matters

Single-block reorganizations are usually part of normal proof-of-work operation, but they still matter because they touch the practical limits of transaction finality. For exchanges, custodians, and payment services, repeated short reorgs can shape how quickly a Bitcoin transaction is treated as settled, especially for larger transfers or automated systems.

The latest case also keeps attention on mining competition and network propagation. When multiple large pools find blocks at nearly the same time, the chain selection process works as designed, but a higher frequency of these events can draw closer scrutiny to how efficiently blocks spread across the network and how concentrated mining activity may affect orphan risk.