BITCOIN MOIEXPLORER

DIFFICULTY · LIVEASERT · 2 H HALF-LIFEupdated just now

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

21.72 M first easing halving in 21 m 13 s
21.72 M before any easing
4 h 25 m against 60 s per block since genesis
starts 20 min after the last block last block 47 s ago
427.31 TH/s pool (shares, 10 min)
3 m 38 s at the required difficulty and that hashrate
now
≈ 9 h 26 m

the node itself reports 21.72 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

5.00 M10.00 M20.00 M50.00 M09:3509:4009:4509:5009:5510:00UTC10-minute level60-second levelblock 30 · 2026-11-05 09:37:21 UTC · difficulty 25.15 Mblock 31 · 2026-11-05 09:39:32 UTC · difficulty 24.10 Mblock 32 · 2026-11-05 09:41:42 UTC · difficulty 23.94 Mblock 33 · 2026-11-05 09:44:12 UTC · difficulty 23.78 Mblock 34 · 2026-11-05 09:50:22 UTC · difficulty 23.57 Mblock 35 · 2026-11-05 09:59:11 UTC · difficulty 22.88 Mblock 36 · 2026-11-05 10:01:22 UTC · difficulty 21.87 Mnownow · 2026-11-05 10:02:09 UTC · required 21.72 M for block 37
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
HASHRATElinear · same time axis
0 TH/s237 TH/s475 TH/s712 TH/s949 TH/s09:3509:4009:4509:5009:5510:0010-min needs 155.48 TH/spool · 2026-11-05 09:34:00 UTC · 414.56 TH/s (10-min shares)pool · 2026-11-05 09:35:00 UTC · 441.91 TH/s (10-min shares)pool · 2026-11-05 09:36:00 UTC · 440.00 TH/s (10-min shares)pool · 2026-11-05 09:37:00 UTC · 446.89 TH/s (10-min shares)pool · 2026-11-05 09:38:00 UTC · 450.89 TH/s (10-min shares)pool · 2026-11-05 09:39:00 UTC · 437.73 TH/s (10-min shares)pool · 2026-11-05 09:40:00 UTC · 429.67 TH/s (10-min shares)pool · 2026-11-05 09:41:00 UTC · 441.63 TH/s (10-min shares)pool · 2026-11-05 09:42:00 UTC · 446.77 TH/s (10-min shares)pool · 2026-11-05 09:43:00 UTC · 440.83 TH/s (10-min shares)pool · 2026-11-05 09:44:00 UTC · 429.67 TH/s (10-min shares)pool · 2026-11-05 09:45:00 UTC · 405.06 TH/s (10-min shares)pool · 2026-11-05 09:46:00 UTC · 410.37 TH/s (10-min shares)pool · 2026-11-05 09:47:00 UTC · 399.71 TH/s (10-min shares)pool · 2026-11-05 09:48:00 UTC · 391.87 TH/s (10-min shares)pool · 2026-11-05 09:49:00 UTC · 410.35 TH/s (10-min shares)pool · 2026-11-05 09:50:00 UTC · 429.64 TH/s (10-min shares)pool · 2026-11-05 09:51:00 UTC · 430.69 TH/s (10-min shares)pool · 2026-11-05 09:52:00 UTC · 425.25 TH/s (10-min shares)pool · 2026-11-05 09:53:00 UTC · 430.56 TH/s (10-min shares)pool · 2026-11-05 09:54:00 UTC · 444.11 TH/s (10-min shares)pool · 2026-11-05 09:55:00 UTC · 445.18 TH/s (10-min shares)pool · 2026-11-05 09:56:00 UTC · 443.51 TH/s (10-min shares)pool · 2026-11-05 09:57:00 UTC · 448.37 TH/s (10-min shares)pool · 2026-11-05 09:58:00 UTC · 446.47 TH/s (10-min shares)pool · 2026-11-05 09:59:00 UTC · 445.23 TH/s (10-min shares)pool · 2026-11-05 10:00:00 UTC · 441.90 TH/s (10-min shares)pool · 2026-11-05 10:01:00 UTC · 424.71 TH/s (10-min shares)pool · 2026-11-05 10:02:00 UTC · 429.39 TH/s (10-min shares)pool · 2026-11-05 10:03:00 UTC · 387.69 TH/s (10-min shares)block 30 · 2026-11-05 09:37:21 UTC · implied 216.01 TH/s (interval 8 m 20 s, header times) - an estimateblock 31 · 2026-11-05 09:39:32 UTC · implied 790.23 TH/s (interval 2 m 11 s, header times) - an estimateblock 32 · 2026-11-05 09:41:42 UTC · implied 790.87 TH/s (interval 2 m 10 s, header times) - an estimateblock 33 · 2026-11-05 09:44:12 UTC · implied 680.82 TH/s (interval 2 m 30 s, header times) - an estimateblock 34 · 2026-11-05 09:50:22 UTC · implied 273.62 TH/s (interval 6 m 10 s, header times) - an estimateblock 35 · 2026-11-05 09:59:11 UTC · implied 185.76 TH/s (interval 8 m 49 s, header times) - an estimateblock 36 · 2026-11-05 10:01:22 UTC · implied 700.96 TH/s (interval 2 m 14 s, seen times) - an estimateUTC
pool hashrate (10-min windows of accepted shares)implied network hashrate per block: difficulty × 2^32 / interval (a noisy estimate)hashrate the current difficulty needs for 1- and 10-minute blocks
BLOCK INTERVALStarget 60 s · log scale
10 s60 s10 minblock 30 · 2026-11-05 09:37:21 UTC · 8 m 20 s after the previousblock 31 · 2026-11-05 09:39:32 UTC · 2 m 11 s after the previousblock 32 · 2026-11-05 09:41:42 UTC · 2 m 10 s after the previousblock 33 · 2026-11-05 09:44:12 UTC · 2 m 30 s after the previousblock 34 · 2026-11-05 09:50:22 UTC · 6 m 10 s after the previousblock 35 · 2026-11-05 09:59:11 UTC · 8 m 49 s after the previousblock 36 · 2026-11-05 10:01:22 UTC · 2 m 11 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 427.31 TH/s. At the current base of 21.72 M a block would take about 3 m 38 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.