Bitcoin difficulty rises 4.16% to 132.76 trillion at block 967,680
Source report: 2026-09-19 · Editorial analysis published: 2026-09-19
The September 19 retarget raises the work required per block; miners should separate difficulty impact from price, fees, uptime and power cost.
Analysis and practical implications
This section is our analysis and illustrative calculations, separate from the source report.
What changed at block 967,680
Bitcoin completed its scheduled difficulty retarget at block 967,680, mined at 07:09:05 UTC on 19 September 2026. The block record exposed by mempool.space reports difficulty of 132,757,073,449,487.52. Its mining API records the previous retarget as a 4.163398% increase, which lifts the rounded headline value from about 127.45 trillion to 132.76 trillion. The adjustment is a protocol result derived from block timing, not a forecast, company estimate or change made by a pool.
Why difficulty increased
Bitcoin targets an average interval of roughly ten minutes and recalculates the target every 2,016 blocks. If the previous epoch finishes faster than the reference interval, the next target becomes harder; if it finishes slower, it becomes easier, subject to protocol bounds. A positive adjustment therefore indicates that blocks in the completed window arrived faster than the target on average. It does not directly measure installed nameplate hashrate, because luck, temporary curtailment and timestamp variance affect any short observation.
Immediate revenue effect
Holding every other variable constant, a 4.1634% difficulty increase reduces expected bitcoin earned per unit of hashrate by about 3.997%. The distinction comes from dividing by the new factor: 1/1.041634 minus one. Real revenue can move differently because bitcoin price, transaction fees, pool luck and uptime also change. Operators should update calculators with the new difficulty rather than simply subtracting 4.16% from yesterday’s cash revenue.
Operational break-even check
Recalculate each miner by accepted hashrate and wall power, not specification-sheet hashrate alone. Include pool fee, rejected shares, cooling, transformer loss, demand charges and curtailment credits. A unit near break-even before the retarget may become negative while a newer efficient unit remains profitable. The proper decision can be underclocking, moving to a cheaper tariff, using heat productively or shutting down for selected hours; it is not automatically permanent retirement.
What the next estimate means
Soon after a retarget, projected next difficulty is based on very few blocks and is highly unstable. At the time of verification, the new epoch had only begun, so a negative estimate was not a reliable forecast. Weather, power-market events, equipment deployment and ordinary block luck can move it materially before block 969,696. Treat live percentages as a scenario, record the observation time, and wait for a meaningful part of the epoch before planning around them.
Data boundary
The confirmed facts are the block height, timestamp, encoded difficulty and completed retarget. Hashrate shown by explorers is an estimate derived from blocks, while miner profitability requires current price, fee and power inputs. asic.tools therefore reports the protocol event separately from operational scenarios. Operators should preserve the block identifier in their records and rerun their own model with the tariff and performance data that apply to their site.
Source: mempool.space ↗
Mining calculator ↗
