ON-CHAIN METRIC
Mining Difficulty
How does Bitcoin reset proof-of-work difficulty every 2,016 blocks to target a ten-minute average?
Open the Mining & Network dashboard
Bitcoin mining difficulty expresses how hard it is, relative to a reference target, to find a block that satisfies the network’s proof-of-work rule. The protocol retargets it every 2,016 blocks.
The aim is to keep average block production near ten minutes. Because the schedule is block-based, a difficulty period is only approximately two weeks.
How the adjustment works
The network compares how long the previous retarget window took with the target duration of 1,209,600 seconds. If blocks arrived too quickly, difficulty rises; if they arrived too slowly, it falls, subject to protocol limits.
Difficulty is a consensus parameter recorded by the network. It is not a direct measurement or “confirmed version” of current hashrate.
What an adjustment implies
A downward adjustment means the preceding window produced blocks more slowly than target, consistent with lower average hashrate than the difficulty setting expected. An increase means the reverse.
Hashrate can change again immediately after a retarget, so difficulty always describes a lagged window. It cannot prove how many machines joined or left.
What difficulty does not tell you
It does not identify miners, locations, energy sources or causes. Price pressure, outages, regulation, seasonal curtailment and new hardware can all affect the observed block rate.
Difficulty also does not predict price directly. It is part of mining economics and supply scheduling, not a directional market signal.
How to read it
Large increase. The prior window found blocks materially faster than target.
Increase. Difficulty rose to offset faster average block production.
Little change. The prior window finished close to target.
Decrease. Difficulty fell after slower average block production.
Large decrease. A substantial slowdown occurred; external context is needed to explain why.
Mining difficulty updates inside the Mining & Network dashboard, alongside hashrate, block interval and epoch views.
Common questions
How often does difficulty change?
Every 2,016 blocks, which is roughly fourteen days when blocks average ten minutes.
Is difficulty the same as hashrate?
No. Difficulty is the protocol-set target parameter. Hashrate is estimated from difficulty and observed block production.
What causes a downward adjustment?
The previous window took longer than its target. Lower average hashrate is one explanation; the series alone cannot identify the operational cause.
Does difficulty affect miner revenue?
It affects each miner’s expected share of block discovery for a given amount of hashpower. Revenue still depends on price, subsidy, fees and competition.
Can difficulty decline for several periods?
Yes. It can keep falling while average block production remains slower than target at each retarget.
ON-CHAIN METRIC
Mining Difficulty
How does Bitcoin reset proof-of-work difficulty every 2,016 blocks to target a ten-minute average?
Open the Mining & Network dashboard
Bitcoin mining difficulty expresses how hard it is, relative to a reference target, to find a block that satisfies the network’s proof-of-work rule. The protocol retargets it every 2,016 blocks.
The aim is to keep average block production near ten minutes. Because the schedule is block-based, a difficulty period is only approximately two weeks.
How the adjustment works
The network compares how long the previous retarget window took with the target duration of 1,209,600 seconds. If blocks arrived too quickly, difficulty rises; if they arrived too slowly, it falls, subject to protocol limits.
Difficulty is a consensus parameter recorded by the network. It is not a direct measurement or “confirmed version” of current hashrate.
What an adjustment implies
A downward adjustment means the preceding window produced blocks more slowly than target, consistent with lower average hashrate than the difficulty setting expected. An increase means the reverse.
Hashrate can change again immediately after a retarget, so difficulty always describes a lagged window. It cannot prove how many machines joined or left.
What difficulty does not tell you
It does not identify miners, locations, energy sources or causes. Price pressure, outages, regulation, seasonal curtailment and new hardware can all affect the observed block rate.
Difficulty also does not predict price directly. It is part of mining economics and supply scheduling, not a directional market signal.
How to read it
Large increase. The prior window found blocks materially faster than target.
Increase. Difficulty rose to offset faster average block production.
Little change. The prior window finished close to target.
Decrease. Difficulty fell after slower average block production.
Large decrease. A substantial slowdown occurred; external context is needed to explain why.
Mining difficulty updates inside the Mining & Network dashboard, alongside hashrate, block interval and epoch views.
Common questions
How often does difficulty change?
Every 2,016 blocks, which is roughly fourteen days when blocks average ten minutes.
Is difficulty the same as hashrate?
No. Difficulty is the protocol-set target parameter. Hashrate is estimated from difficulty and observed block production.
What causes a downward adjustment?
The previous window took longer than its target. Lower average hashrate is one explanation; the series alone cannot identify the operational cause.
Does difficulty affect miner revenue?
It affects each miner’s expected share of block discovery for a given amount of hashpower. Revenue still depends on price, subsidy, fees and competition.
Can difficulty decline for several periods?
Yes. It can keep falling while average block production remains slower than target at each retarget.