Blocks until the retarget
blocksBlocks between the latest block and the next retarget height.
When is the next Bitcoin difficulty adjustment, and how big will it be?
Blocks left in the current epoch, the projected date of the next retarget and the change it would make at the epoch's pace so far.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Blocks left, the projected date and the estimated change.
Blocks between the latest block and the next retarget height.
The projected time of the retarget block, from the epoch's average block interval so far.
The difficulty change the epoch's pace so far implies, computed the way the rules will compute it at the retarget.
The average interval between blocks in the current epoch so far, against the ten-minute target.
The estimated change recomputed at every block of the current epoch, which narrows as the epoch fills.
Each block's time since the block before it in the current epoch, with the epoch's running average drawn across.
Recent retargets and how the estimates compared with what happened.
The difficulty change at the most recent retarget, against the epoch before it.
How far the estimate made at each epoch's midpoint was from the actual change, averaged over the retargets in the period.
The difficulty change at each retarget over the selected period.
Each retarget with its height, date, new difficulty, change, the epoch's length in days and the estimate made at the epoch's midpoint.
The next Bitcoin difficulty adjustment happens at the end of the current epoch, and this dashboard counts the blocks left until it, projects its date and estimates how much difficulty will change if blocks keep arriving at this epoch's pace. The rules set the change: difficulty scales by how long the epoch's blocks took against a target of two weeks.
The estimate firms up as the epoch fills. Early in an epoch a few fast or slow blocks swing it widely; near the end it is close to exact, because most of the epoch's time is already on the chain. The dashboard draws the estimate as it moved through the epoch, names the block it was computed at and shows how past estimates compared with the changes that followed.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →Read from chain state and history
At the end of every epoch, about two weeks of blocks, each node recomputes the mining target from how long the epoch took. If blocks came faster than every ten minutes on average, difficulty rises; if slower, it falls, so block times return toward the target.
From the epoch so far: the average interval between its blocks is extended over the blocks left, and the projected epoch time is compared with the target time. The closer the epoch is to its end, the more accurate the estimate.
The rules limit each retarget to a factor of four up or down. In practice changes are far smaller, because hashrate rarely moves that much within two weeks.
When hashrate grows during an epoch, miners find blocks faster than the current difficulty expects. The next retarget raises difficulty to match, and until then blocks keep arriving early. Single intervals also vary widely, because finding a block is random.
Not directly. Faster blocks clear the mempool sooner and can lower fee rates for a while, and slower blocks do the opposite. The fees themselves are set by users bidding for block space, not by difficulty.
Bitcoin's estimated network hashrate and mining difficulty, epoch by epoch, with every retarget, record and drop read from block headers.
BitcoinBlocks left until the next Bitcoin halving, its date projected from recent block times and the block reward before and after it.
BitcoinWhich pools found Bitcoin's blocks over the last day, week and month, the hashrate share each implies and how concentrated mining is.
BitcoinWhat Bitcoin miners earn per day and per unit of hashrate, in BTC and USD, split into block subsidy and fees, from every block's coinbase.
BitcoinThe fee rate to confirm a Bitcoin transaction in the next block, an hour or a day, with mempool size and the fees recent blocks really paid.
BitcoinHow much bitcoin has been issued, how much is issued each day, how much is left to mine and how much can never be spent.
BitcoinStart free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.