Bitcoin difficulty fell 5% as slower mining triggered a retarget

Bitcoin’s mining difficulty fell 5.004% at block 957,600 on July 11, 2026, reducing the network-wide threshold from 133.87 trillion to 127.17 trillion. The block’s timestamp was 20:09:11 UTC, and its encoded difficulty value was 127,170,500,429,035.19.

The adjustment was a protocol response, not a vote or discretionary intervention. Bitcoin recalculates difficulty every 2,016 blocks to steer average block production back toward roughly ten minutes. Blocks in the epoch ending July 11 arrived too slowly for that target, so the next epoch began with less work required, on average, to find a valid block.

The change mattered most to miners. With bitcoin’s dollar price, transaction fees, equipment efficiency and electricity costs held constant, a lower difficulty improves the expected bitcoin output of each unit of hashpower. It also showed the network absorbing a reduction in effective mining activity without changing issuance rules or relying on a central operator.

What the chain records

Mempool.space identifies block 957,600 by the hash 00000000000000000000c1294b131fbf6d489c74e52c13e905f003ad9ccb9ba2. The explorer attributes it to Foundry USA and records 4,054 transactions, a 3.125 BTC subsidy and 0.03832271 BTC in transaction fees. Those block details establish the height, timestamp and new difficulty; they do not, by themselves, explain why individual miners added or removed machines.

The preceding difficulty was 133,869,853,540,305.41. The new value was 127,170,500,429,035.19. Subtracting the two yields a reduction of about 6.699 trillion difficulty units; dividing that difference by the preceding value produces 5.004%, rounded to three decimal places. Contemporaneous coverage generally rounded the move to 5.00%.

Hashrate estimates require more caution. There is no network sensor counting every active machine. Analysts infer effective hashrate from the rate at which valid blocks appear, so short measurement windows contain substantial luck-driven variance. Hashrate Index’s July 13 review estimated that its seven-day simple moving average had declined from 939 exahashes per second to 879 EH/s by July 13. That is post-event context, not an exact July 11 measurement, and it should not be substituted for the deterministic difficulty value recorded in the block.

A mechanical relief valve

Difficulty measures how hard it is, statistically, to produce a header below Bitcoin’s proof-of-work target. A 5.004% reduction did not make previously invalid transactions valid, change the 3.125 BTC block subsidy or alter the 21 million bitcoin supply limit. It changed only the proof-of-work threshold for the new epoch.

The adjustment also did not prove that mining had become profitable. Profitability remained operator-specific and depended on bitcoin price, fee revenue, power contracts, machine efficiency, uptime and financing. The protocol lowered the competitive threshold, but it could not determine any miner’s balance sheet.

What July 11 established

The defensible event-day conclusion is narrow: effective block production during the completed 2,016-block epoch lagged Bitcoin’s target enough to trigger a 5.004% downward retarget at height 957,600. The network then continued under difficulty 127.17 trillion.

That is consequential because the retarget mechanism is Bitcoin’s automatic answer to changing hashpower. It aims to preserve the cadence of confirmations and new issuance even as miners enter, leave or curtail operations. July 11 supplied a clean, on-chain example of that mechanism working as designed. It did not establish the cause of the hashrate change, forecast the next adjustment or support a conclusion about bitcoin’s market price.