Bitcoin's mining difficulty rose to 140.58T at block 971,712 on October 16, 2026 (UTC), up 5.92% from the previous epoch's 132.72T. For miners maintaining the same hashrate, that increase means roughly 5.59% less expected BTC output over the same period, assuming the reward per block and uptime remain unchanged.

What Happened at Block 971,712

The October 16 adjustment established the difficulty for the epoch beginning at block 971,712. BTC.network's dated adjustment report lists the move from 132.72T to 140.58T, while ChainQuery's node-backed dashboard independently identifies the epoch's starting block and date alongside the 140.58T difficulty level. Adjustment report · Node-backed dashboard

This is an applied difficulty level rather than a forecast for an unfinished epoch. The block header stores the proof-of-work target in compact form; difficulty expresses how demanding that target is relative to Bitcoin's reference target. Bitcoin Core implementation

Effect on Mining Revenue per Hash

A higher difficulty lowers the probability that any single hash will satisfy the target required for a valid block. Holding hashrate, block subsidy, average transaction fees per block, and uptime constant, a miner therefore expects to find fewer blocks and earn less BTC over the same period. The adjustment does not itself change the miner's share of total network hashrate. Proof-of-work explanation

The relationship between difficulty and expected output is inverse. Using the reported 5.92% increase:

Expected BTC output reduction ≈ [1 − 1 / (1 + 0.0592)] × 100 ≈ 5.59%.

This is an expected-value illustration, not a guaranteed change in a miner's next payout. Actual receipts also depend on pool payout mechanics, mining luck where applicable, transaction fees, and operational uptime. BTC price affects the fiat value of those receipts; it does not directly change the amount of BTC earned.

Why Difficulty Rose This Epoch

Bitcoin adjusts its proof-of-work target every 2,016 blocks. For the adjustment at block 971,712, the preceding epoch covered blocks 969,696 through 971,711.

The protocol uses the difference between the timestamps of the first and last blocks in that epoch—a span of 2,015 block intervals—and compares it with a 1,209,600-second (14-day) reference window. A shorter measured span leads to a lower target and higher difficulty; a longer span leads to a higher target and lower difficulty. This timestamp calculation is implemented in Bitcoin Core. Retarget implementation

The upward adjustment reflects a preceding measurement window shorter than the reference period. It does not, by itself, establish precisely how much hardware joined the network or distinguish changes in hashrate from variation in block discovery.

Difficulty and Hashrate Measure Different Things

Difficulty is derived from the network's required proof-of-work target and remains fixed between mainnet retarget boundaries. Network hashrate is an estimate based on difficulty and observed block production. Providers can report different estimates because they use different measurement windows or smoothing methods.

Neither figure is interchangeable with an individual miner's hashrate. ASIC software reports device-level performance, while a pool estimates a worker's hashrate from submitted shares and their assigned difficulty. Short-term differences between these readings do not automatically indicate an equipment problem.

Practical Considerations for Miners

Following a retarget, miners may find it useful to update expected BTC output and breakeven calculations that used the previous 132.72T difficulty. Electricity costs, hosting arrangements, hardware performance, and the fiat value of BTC remain separate inputs to profitability.

If pool-side hashrate changes at the same time, compare it with device telemetry over a suitable measurement period before attributing the change to equipment performance. A network difficulty adjustment alone does not establish that a miner's machines are performing differently.

For a fuller walkthrough of retarget calculations, see How to Understand Bitcoin Difficulty Adjustments Before Starting.

When Is the Next Bitcoin Difficulty Adjustment?

The next retarget occurs at block 973,728, which is 2,016 blocks after the current epoch's starting height. Its calendar date depends on how quickly blocks are found. ChainQuery's dashboard identifies this next retarget height and provides a changing timing estimate. Next retarget data

The direction depends on the completed epoch's timestamp span relative to the 14-day reference window. A projected date or percentage change should remain labeled as an estimate until the adjustment occurs.

Where to Verify the Data

The October 16 adjustment figures are recorded in BTC.network's dated report. ChainQuery's live dashboard provides a separate check of the current difficulty, epoch start, and next retarget height. Live dashboards change over time, so readers checking this historical adjustment should distinguish its recorded figures from a later epoch's current values.

For the adjustment mechanics, consult the Bitcoin Developer Guide and Bitcoin Core implementation linked below. Sources were accessed on October 20, 2026.

FAQ

What does a 5.92% difficulty increase mean for Bitcoin miners?

At unchanged hashrate, reward per block, and uptime, expected BTC output over the same period falls by approximately 5.59%. Actual payouts can differ because of pool payout mechanics, fees, and mining luck.

Does higher difficulty mean my ASIC is less efficient?

No. Difficulty does not change an ASIC's measured energy efficiency. Efficiency in joules per terahash (J/TH) is calculated from power consumption and the corresponding device hashrate, not from network difficulty.

When is the next Bitcoin difficulty adjustment?

At block 973,728. The block height is known, but the date and adjustment percentage remain estimates until the epoch is completed.

References

• Epoch 482: Bitcoin Difficulty Jumps 5.9% — BTC.network, October 16, 2026; used for the reported adjustment figures only.
• Bitcoin Difficulty — ChainQuery; live difficulty and retarget dashboard.
• Block Chain — Bitcoin Developer Guide — proof-of-work and difficulty adjustment mechanics.
• Bitcoin Core: pow.cpp — target and retarget implementation.