Bitcoin’s network experienced a rare two-block chain reorganization (reorg) on March 23, 2026, around block height 941,880–941,882. This event involved competing chains from major mining pools, but the network resolved it quickly according to its standard consensus rules, with no impact on users, funds, or transaction security.
At block 941,881, AntPool and Foundry USA (the largest mining pool) each found a valid block within about 12 seconds of each other (around 15:49 UTC). This created a temporary fork: some nodes followed one chain, others the competing one.
On the next block (941,882), ViaBTC extended AntPool’s chain, while Foundry extended its own. This resulted in two competing chains, each two blocks long. Foundry then mined several consecutive blocks; reports vary between six and seven in a row, up to around 941,885–941,886.
Because its chain accumulated more proof-of-work faster, it became the “longest” (highest cumulative difficulty) chain. The network automatically adopted Foundry’s version as the canonical blockchain. The two blocks from AntPool and ViaBTC were orphaned also called stale blocks. Those miners received no block rewards, and any transactions unique to those blocks returned to the mempool for later inclusion.
Bitcoin developer b10c; a well-known observer first highlighted the event, noting it as a “rare-ish two block fork/reorg” with Foundry dominating the streak. Single-block reorgs happen regularly roughly once every couple of weeks on average historically when two miners solve a block nearly simultaneously.
Two-block reorgs are much rarer because they require the tie to persist for a full extra block cycle. They occur a few dozen times in Bitcoin’s entire history. Deeper reorgs (3+ blocks) are extremely uncommon and have never been observed at scale in modern Bitcoin.
The protocol worked exactly as designed: nodes always follow the chain with the most accumulated computational work. No double-spends succeeded, and no funds were lost—any affected transactions simply get re-confirmed shortly after.
This reorg occurred days after a significant mining difficulty drop of nearly 8%; one of the larger downward adjustments in 2026. It has drawn attention to hashrate concentration: Foundry USA controls a substantial share around 30%+ in recent estimates. AntPool and ViaBTC have smaller but notable shares. When one pool has a larger share, the probability of it winning short-term “block races” during forks increases, making visible streaks (and thus reorgs) statistically more likely.
This is not a bug or attack—it’s a natural outcome of Proof-of-Work economics, especially post-halving when margins tighten and less efficient miners exit or consolidate. Some analysts view it as an on-chain signal of industry contraction and centralization pressures.
However, it does not threaten Bitcoin’s overall security model. A true 51% attack would require sustained, deliberate dominance far beyond a short streak. For everyday transactions, this changes nothing. For high-value transfers, the standard advice remains: wait for 6 confirmations ~1 hour to minimize any theoretical reorg risk.
Exchanges and services already follow this practice and were unaffected. Bitcoin’s decentralized consensus proved resilient once again. Temporary forks and reorgs are features of how the network achieves agreement without a central authority, not signs of weakness.
Negligible impact. Confirmations remain reliable; the network processed the recent reorg without issues. High-Value Transactions: Stick to 6+ confirmations ~1 hour as a conservative buffer against rare reorgs. Watch hashrate distribution charts. Sustained top-pool dominance above 40–50% for one entity would warrant more scrutiny.
If centralization worsens, it could pressure Bitcoin’s censorship-resistance narrative, potentially affecting adoption or regulatory views. Solutions include encouraging geographic diversity, smaller-pool usage, Stratum V2 adoption, and home/solo mining where feasible though economically challenging.
Bitcoin’s security ultimately rests on the assumption that a majority of hashpower acts honestly due to aligned incentives—not perfect distribution. The recent reorg was a reminder of concentration risks amid 2026’s tough mining economics, but also proof that the protocol handles short-term forks as designed. The network continues to hash at hundreds of exahashes per second, making it the most secure public blockchain by computational expenditure.
