Binance Pool Produced 1 Bitcoin Block Before Nov. 10 Shutdown

Binance’s Bitcoin mining pool produced just one block in seven days before its scheduled Nov. 10 shutdown. That output represented about 0.11% of the roughly 925 blocks the Bitcoin network generated over the same period, according to CoinDesk’s Nov. 9 report citing blockchain data platform mempool.space.

The network produced roughly 132 blocks per day over those seven days, while Binance Pool produced none in the 24 hours before the report. Its latest block, No. 974743, arrived at 1:15 a.m. UTC on Nov. 6 and included 1,353 transactions. Mining rewards and fees totaled about 3.134 BTC.

What changes at the Nov. 10 shutdown?

Binance announced last month that it would close the mining-pool operation. Starting at 7 a.m. UTC on Nov. 10, the company plans to disconnect miners and terminate four related services:

• Block reward service.
• Cloud mining.
• Pool savings products.
• Transaction acceleration service.

The shutdown spans mining operations and adjacent customer products. For miners, the immediate task is to redirect their connections before the cutoff; for customers, the termination ends access to the other three services. The announcement gives participants a defined window to move rather than leave the service without a replacement route.

How much computing power is leaving?

The contraction predates the closure. Binance Pool’s hashrate fell to about 9.2 exahashes per second last month from roughly 26 EH/s in December 2025. That 65% decline over about 10 months left the pool operating at roughly 35% of its December 2025 level.

Mining pools combine miners’ computing resources to generate blocks and distribute rewards, but block production remains probabilistic. A seven-day sample cannot establish the pool’s exact hashrate on its own. The reported hashrate trend provides the stronger measure of the contraction, while the one-block week offers a snapshot of output rather than a precise capacity reading.

Where can miners move?

CoinDesk identified Foundry USA, Antpool and F2Pool as established pools that could receive hashpower from departing participants. The report did not confirm any transfers, and mining output alone cannot measure the capacity involved with precision.

Those operators already command a large share of the Bitcoin network. If Binance Pool’s connected computing power shifts to them, their block production and share of pooled mining could increase, further concentrating coordination among major operators.

What does this change for miners? It changes where miners submit work and how they receive rewards, without changing the underlying Bitcoin protocol. The practical constraint is the deadline: miners must reroute connections through another pool or cease using Binance’s infrastructure before 7 a.m. UTC on Nov. 10.

Cloud mining users, pool-savings customers and transaction-acceleration users face the same cutoff. All four services end at the scheduled time, rather than only pool participation.

After the 7 a.m. UTC Nov. 10 cutoff, block-production data over subsequent weeks will show which pools absorb the departing hashpower and whether the change strengthens the industry’s largest operators.