BITCOIN MOIEXPLORER

DIFFICULTY · LIVEASERT · 2 H HALF-LIFEupdated just now

what block 13 must meet, worked out from the consensus rules and the chain's own headers

31.34 M first easing halving in 12 m 15 s
31.34 M before any easing
3 h 30 m against 60 s per block since genesis
starts 20 min after the last block last block 9 m 45 s ago
221.34 TH/s pool (shares, 10 min)
10 m 08 s at the required difficulty and that hashrate
≈ 2 m 37 s
≈ 13 h 01 m

the node itself reports 31.34 M for the next block without easing; the base above is computed independently and should match it.

Estimates: the hashrate stays where it is and blocks arrive at their expected pace; ASERT alone, the easing can make single blocks faster; 1-minute means within 10 % of 60 s.

DIFFICULTY OVER TIMELOG SCALE

200.00 k500.00 k1.00 M2.00 M5.00 M10.00 M20.00 M50.00 M100.00 M06:0007:0008:00UTC10-minute level60-second levelblock 1 · 2026-11-05 05:31:09 UTC · difficulty 3.14 Mblock 2 · 2026-11-05 06:07:50 UTC · difficulty 330.15 kblock 3 · 2026-11-05 06:39:52 UTC · difficulty 1.07 Mblock 4 · 2026-11-05 07:11:01 UTC · difficulty 1.80 Mblock 5 · 2026-11-05 07:33:41 UTC · difficulty 24.15 Mblock 6 · 2026-11-05 07:38:52 UTC · difficulty 42.62 Mblock 7 · 2026-11-05 07:44:52 UTC · difficulty 41.60 Mblock 8 · 2026-11-05 08:08:22 UTC · difficulty 20.21 Mblock 9 · 2026-11-05 08:08:52 UTC · difficulty 35.50 Mblock 10 · 2026-11-05 08:09:22 UTC · difficulty 35.60 Mblock 11 · 2026-11-05 08:09:52 UTC · difficulty 35.70 Mblock 12 · 2026-11-05 08:33:53 UTC · difficulty 8.95 Mnownow · 2026-11-05 08:43:38 UTC · required 31.34 M for block 13
mined block (from its header bits)ASERT base for the next blockrequired difficulty, with the easing stepsbetween the 60-second and 10-minute levels at the measured hashrate
BLOCK INTERVALStarget 60 s · log scale
10 s60 s10 minblock 1 · 2026-11-05 05:31:09 UTC · 31 m 07 s after the previousblock 2 · 2026-11-05 06:07:50 UTC · 36 m 41 s after the previousblock 3 · 2026-11-05 06:39:52 UTC · 32 m 02 s after the previousblock 4 · 2026-11-05 07:11:01 UTC · 31 m 09 s after the previousblock 5 · 2026-11-05 07:33:41 UTC · 22 m 40 s after the previousblock 6 · 2026-11-05 07:38:52 UTC · 5 m 11 s after the previousblock 7 · 2026-11-05 07:44:52 UTC · 6 m 00 s after the previousblock 8 · 2026-11-05 08:08:22 UTC · 23 m 30 s after the previousblock 9 · 2026-11-05 08:08:52 UTC · 30 s after the previousblock 10 · 2026-11-05 08:09:22 UTC · 30 s after the previousblock 11 · 2026-11-05 08:09:52 UTC · 30 s after the previousblock 12 · 2026-11-05 08:33:53 UTC · 24 m 01 s after the previous

WHAT ASERT DOES

Every block has a schedule: block n is due 60 s × n after genesis. ASERT compares the last block's time with that schedule. For every 2 hours the chain is behind, the difficulty halves; for every 2 hours ahead, it doubles. It started at 100.00 M, which needs about 7.2 PH/s for 60-second blocks, and it looks only at the schedule, so one slow or fast block cannot swing it.

WHAT THE EASING DOES

If no block has been found 20 minutes after the last one, the block being mined may use a lower difficulty: half after 22 minutes, a quarter after 24, and so on, halving every 2 minutes by its own timestamp. It applies to that one block only; the next block starts again from the ASERT base. A block must also come at least 30 seconds after the one before it.

WHY BLOCKS ARE SLOW RIGHT NOW

The miners now bring about 221.34 TH/s. At the current base of 31.34 M a block would take about 10 m 08 s on average, so most blocks come in through the easing, 20-30 minutes after the one before. Each slow block puts the chain further behind its schedule, and every 2 hours behind halves the base, so block times shorten step by step until the difficulty meets the hashrate.

The rules are consensus code: ASERT in src/pow.cpp, the launch rules (R1, R2) in the chain parameters. This page recomputes them from the block headers; /api/difficulty has the numbers as JSON.