Cryptocurrency Network Difficulty

Current Bitcoin, Litecoin, Dogecoin and Bitcoin Cash difficulty in one table: how it is about to change and when it retargets. Data comes from RuPool's own full nodes and refreshes every minute.

CoinCurrent difficultyChangeRetargetDetails
Bitcoin
BTC · 2016 blocks
134.82T

no forecast

1,904 blocks left · ~Nov 28, 2026, 04:43 UTCDetails
Litecoin
LTC · 2016 blocks
94.73M+0.82%
retarget forecast
287 blocks left · ~Nov 15, 2026, 11:15 UTCDetails
Dogecoin
DOGE · DigiShield
43.02M+2.13%
24-hour average
every block · DigiShieldDetails
Bitcoin Cash
BCH · ASERT
502.96B-0.45%
24-hour average
every block · ASERTDetails

What mining difficulty is

Mining difficulty is a number that tells you how much work it takes on average to find a block. Every network tunes it to its total hashrate so that blocks keep arriving at the planned pace: new hardware comes online and difficulty goes up, miners switch off and it comes down.

For a miner, network difficulty is the biggest external factor in profitability after the coin price. At a constant hashrate, your share of blocks, and with it your income in coins, is inversely proportional to difficulty. On an FPPS pool such as RuPool this shows up directly: the reward per share follows difficulty.

Two ways to adjust difficulty

The coins in the table above use two families of algorithms. The first is epoch-based: difficulty stays fixed for a set number of blocks and is then recalculated once, based on how quickly the epoch went by. The date of the next adjustment is known in advance, and its size can be forecast from the average block time.

The second adjusts at every block. The network keeps nudging difficulty based on recent block times or on how far the chain has drifted from an ideal schedule, so there is no single next adjustment to wait for. For these coins the daily average and its trend say more than the instantaneous value.

  • Epochs: predictable and easy to forecast, but slow to react; if hashrate leaves suddenly, blocks stay slow until the epoch ends.
  • Every block: reacts quickly to hashrate arriving or leaving, but the instantaneous value is noisy and needs averaging.

Why difficulty can't be compared across coins

Difficulty is a relative measure. It is tied to the network's hash function and to its target block time. A SHA-256 hash and a Scrypt hash cost hardware very different amounts of work, so the numbers for coins on different algorithms aren't comparable. Even on the same algorithm, a network with one-minute blocks and one with ten-minute blocks need different hashrates at the same difficulty.

What does compare across coins is the trend: how many percent difficulty moved over a day, a week or an epoch, and how that stacks up against your own hashrate and the coin price. Each coin page explains how that network adjusts difficulty and shows its full history.

Frequently asked questions

Why do some coins have an adjustment forecast and others don't?

A forecast only makes sense for epoch-based adjustment: you know how many blocks remain until the change, and the average block time lets you estimate its size. Coins that adjust at every block change difficulty continuously, so their pages show the daily average and its trend instead.

Can you compare difficulty between SHA-256 and Scrypt coins?

Not directly. The difficulty value depends on the hash function and the target block time, so a bigger number for one coin doesn't mean it is harder to mine than a coin with a smaller one. Compare percentage changes and the income your hardware actually earns.

Is rising or falling difficulty better for a miner?

All else equal, falling difficulty means more coins and rising difficulty means fewer. But difficulty rarely moves on its own: it drops when miners leave because of a weaker price or expensive power, and rises when mining becomes more profitable. That is why it is worth reading together with the price.

Where does the difficulty data come from?

From the full nodes RuPool runs for its own operation. Values refresh every minute, and no third-party services are used for this data.