Bitcoin Difficulty Adjustment Explained: Every 2,016 Blocks

The short answer: Bitcoin retargets after a block window

Bitcoin mainnet adjusts its proof-of-work target at retarget boundaries, every 2,016 blocks. Bitcoin Core v31.1 sets a target spacing of 10 minutes and a target timespan of 14 days; 2,016 × 10 minutes equals two weeks. The network compares how quickly the recent window arrived with that target period, then changes how hard it is for a block hash to qualify.

This is a target average, not a block-by-block clock. Individual blocks can arrive much sooner or later than ten minutes. A retarget does not promise that the next block—or every future block—will arrive on schedule.

What changes when blocks arrive faster or slower?

A block header's proof-of-work hash must be at or below a target. A lower target is harder to hit because fewer possible hashes qualify; a higher target is easier. Bitcoin Core measures the elapsed time for the retarget window and scales the target toward the 14-day timespan.

• If the window arrives faster than its target, the next target moves lower: mining becomes harder.
• If the window takes longer than its target, the next target moves higher: mining becomes easier.
• If it is close to the target, the adjustment is correspondingly smaller.

For an intentionally simplified example, imagine the observed window takes 10 days instead of 14. The target moves down, making qualifying hashes less common in the next period. If a window takes 18 days, the target moves up. These are fictional elapsed times used to explain direction—not current network measurements or a forecast. Bitcoin Core also limits the measured adjustment at each retarget, so one window cannot produce an unlimited jump.

When does the rule run?

The regular mainnet retarget happens at the boundary between 2,016-block periods, not whenever miners add more machines or whenever one slow block appears. Between regular boundaries, the mainnet proof-of-work target normally stays the same. Bitcoin Core has separate special rules for some test networks, so this article describes Bitcoin mainnet rather than every Bitcoin-like chain.

Difficulty, mining and halvings are different ideas

Difficulty adjustment changes the proof-of-work target; it does not change the subsidy paid by a block. Bitcoin's subsidy follows a separate block-height schedule. Read Bitcoin halving explained for that issuance rule.

Mining software searches for a qualifying hash and proposes a block, while full nodes independently check the block against the rules they follow. A retarget does not replace those checks or tell you whether a mining business will make money. See what Bitcoin mining does for the search-and-validation distinction and what a Bitcoin confirmation means for how later blocks build on transaction history.

Read the visual without treating it as a countdown

Start with the 2,016-block window. Then follow the two branches: faster-than-target blocks lower the target; slower-than-target blocks raise it. Both directions aim toward a long-run average near ten minutes, but block arrivals remain variable. You can follow this rule without a wallet, miner, or payment.