Bitcoin mining difficulty rises 5.92% at block 971,712

Bitcoin’s mining difficulty rose 5.92% at block 971,712 on October 16, raising the amount of computing work expected for each valid block after miners completed the preceding 2,016-block period faster than the protocol’s target pace.

Mempool.space’s block record timestamps the boundary block at 12:37:31 UTC, or 8:37:31 a.m. Eastern, and records difficulty at 140,577,680,051,919.6. Newhedge’s historical table lists the preceding level as 132,716,002,350,731 and calculates the realized change at 5.92%.

The adjustment matters immediately to miners because a machine with unchanged hashrate now represents a smaller share of the network’s expected work. It does not change the machine’s rated speed, electricity draw or operating cost by itself, and it says nothing direct about bitcoin’s market price.

The retarget followed a faster epoch

Bitcoin Core changes the proof-of-work target only at a difficulty-adjustment boundary. Its published code checks the block height, looks back across the interval and compares the elapsed timestamps with the target timespan. On mainnet, the interval is 2,016 blocks, designed around an average of approximately 10 minutes per block, or roughly two weeks.

The prior adjustment occurred at block 969,696 on October 3. Newhedge records that move as a 0.03% decline, from about 132.76 trillion to 132.72 trillion. The October 16 increase more than reversed that small reduction and lifted difficulty to its highest displayed level since March 5, when the same table records about 145.04 trillion.

Difficulty is a dimensionless ratio derived from the target encoded in each block header; it is not a hashrate reading. A value of 140.58 trillion must not be described as 140.58 trillion hashes per second, and it does not reveal how many machines are online or where they operate.

Expected output falls less than 5.92%

For a miner holding its own hashrate constant, expected block-finding frequency is inversely proportional to network difficulty. Using Newhedge’s unrounded old and new values, Coinburn calculates the new expected rate at approximately 94.41% of the old rate. That implies about 5.59% less expected bitcoin output per unit of time, assuming the miner’s hashrate, uptime and other conditions do not change.

The distinction between the 5.92% difficulty increase and the 5.59% expected-output reduction is mathematical, not contradictory: the output comparison divides the old difficulty by the new one. It is a long-run expectation, not a promise about any pool payment or a solo miner’s result during a short window.

The calculation also isolates mined bitcoin. It does not establish a 5.59% decline in dollar revenue or profit. Bitcoin’s price, transaction fees, pool fees, rejected shares, maintenance, energy tariffs and curtailment can all change the realized outcome. Individual blocks also carry variable transaction fees on top of the block subsidy.

A protocol response, not a causal verdict

The completed retarget proves that blocks in the measured interval arrived faster than the protocol’s target schedule. It does not prove which miners added capacity, whether newer hardware caused the change or whether the network’s geographic distribution shifted. Hashrate estimates infer computing activity from block production and vary with their measurement window.

Bitcoin.com reported that network hashrate was above one zettahash per second around the adjustment, but that is an estimate tied to its observation window, not a direct census of equipment. Short-window estimates can move sharply because block discovery is probabilistic.

The next scheduled boundary is block 973,728. Any date or percentage estimate for that future adjustment remains provisional until the block is mined. The defensible conclusion for October 18 is narrower: Bitcoin completed a 5.92% upward retarget on October 16, tightening expected mining output for fixed hashrate while leaving each operator’s actual economics dependent on costs, fees, uptime and bitcoin’s price.