Bitcoin saw a block reorganization at height 966500 on September 11, with mempool.space showing that AntPool’s block remained on the main chain while a competing valid block mined by SpiderPool at the same height became stale.

According to the disclosed chain data, AntPool mined a block with 4,359 transactions and a reward of 3.14112795 BTC at 8:30:30 PM KST on September 11. SpiderPool also produced a valid block at the same height. Once the next block was built on top of AntPool’s version, that branch accumulated more work and was recognized as the canonical chain.

In practical terms, SpiderPool’s competing block was treated as a stale block. This is the standard outcome when two miners find blocks at nearly the same time and the network briefly sees two valid branches before one gains the lead.

The report described the incident as the third Bitcoin reorganization within a month and referenced another case involving block 963853 mined by SpiderPool on August 24. No additional details were provided on the earlier events, and no direct operational impact on exchange deposits, withdrawals, or payment services had been confirmed at the time of the report.

Short-range reorganizations are a known part of proof-of-work chain operation because block propagation is not instantaneous across the network. The key issue for market infrastructure is usually not the existence of a brief fork itself, but whether service providers need to wait for additional confirmations before treating transactions as final.

Why It Matters

For Bitcoin users and market infrastructure operators, reorganizations are a reminder that final settlement on a proof-of-work network is probabilistic rather than absolute at the moment a block first appears. Even when the event is brief and resolves normally, exchanges and payment platforms may reassess how quickly they credit transfers or release funds.

The news also matters because repeated reorganizations over a short period can draw closer scrutiny from trading venues, custodians, and merchants that rely on predictable confirmation timing. The broader significance is operational: how Bitcoin-linked services manage settlement risk when competing blocks briefly coexist on the network.