Binance Pool falls to one block in final week before shutdown

Binance Pool produced one Bitcoin block during the seven days preceding a late-November 8 data snapshot, leaving the exchange-operated mining service almost absent from block production immediately before its scheduled closure.

CoinDesk’s review of mempool.space data counted roughly 925 blocks across the network during that window. Binance Pool’s single block therefore represented about 0.11% of observed production, a calculation that describes only the reviewed seven-day period. The pool found no block during the snapshot’s final 24 hours.

The timing matters because Binance plans to disconnect miners and disable its pool infrastructure at 07:00 UTC on November 10. The thin final-week output indicates that much of the pool’s former activity had already disappeared or moved elsewhere before the formal cutoff.

It does not indicate that the underlying mining machines stopped operating. Independent miners can redirect the same equipment to another pool, shifting which operator coordinates their work and distributes rewards without removing that computing power from Bitcoin.

The last identified block

Blockchain explorers identify block 974,743 as Binance Pool’s most recent success in the reviewed period. It was mined at 01:15:54 UTC on November 6 and contained 1,353 transactions.

The block paid 3.13393951 BTC to its miner: the protocol’s 3.125 BTC subsidy plus 0.00893951 BTC in transaction fees. Those figures describe that block only. They do not measure the pool’s revenue for the week because pool participants may receive payments under internal accounting methods that differ from the timing of individual block discoveries.

Miner attribution also has a limitation. Bitcoin’s consensus record establishes the block, timestamp, transactions and reward, while explorer services identify Binance Pool from the block’s coinbase data. The network itself does not maintain an authoritative registry of corporate mining-pool identities.

One week is not a hashrate measurement

Block discovery is probabilistic. A pool can find more or fewer blocks than its computing share would predict over a short interval, so one block in seven days cannot by itself establish Binance Pool’s exact remaining hashrate.

CoinDesk separately assessed the pool’s computing power at approximately 26 exahashes per second in December 2025 and about 9.2 exahashes per second in October 2026. That comparison implies a decline of roughly 65% between those two monthly observations. The estimates are not continuous measurements, and neither the reporting nor Binance’s closure notice provides a final November hashrate reading.

The block-production snapshot is nevertheless consistent with a service approaching shutdown. Binance’s October 13 notice told users to reconfigure miners before the cutoff and said shares submitted afterward would not be accepted, processed or credited.

What closes and what continues

The November 10 action covers Binance Pool, Pool Savings, Cloud Mining, the Transaction Accelerator, mining APIs and related alerts. Eligible shares submitted before 07:00 UTC are supposed to enter the final reward calculation, although payments remain subject to product rules, account status, compliance controls and applicable law.

Binance plans to leave historical pool pages available until 07:00 UTC on November 24. That two-week viewing period does not extend mining or guarantee that every settlement will be completed by then.

Bitcoin itself is not shutting down or changing its consensus rules. The operational question is where former Binance Pool participants redirect their machines and whether that migration increases or reduces concentration among the remaining large pools. The reviewed records do not identify those destinations, quantify migrated hashrate or establish the final distribution after the cutoff.

Coinburn previously reported Binance’s October closure announcement. The new evidence is the final-week production snapshot and independently verifiable last identified block, not a new shutdown decision.