Skip to content
Satoshi Gazette
Data DeskLive

Hashprice & difficulty

Expected sats for one TH/s a day, the fee share of the block reward, difficulty since 2009 and the network’s hashrate.

Expected reward for one TH/s over a day

42.78sats per TH/s per day

from block 975,723’s subsidy plus the average fees of blocks 975,580–975,723

Formula (subsidy + average fee) sats × 86,400 × 10¹² ÷ (difficulty × 2³²)

Today: (312,500,000 + 3,010,782.8) sats × 86,400 × 10¹² ÷ (mempool.space’s difficulty, 148,364,561,003,867.4, × 2³²) = 42.78 sats per TH/s per day.

Subsidy only, the fees left out: 42.37 sats per TH/s per day.

On your node: bitcoin-cli getblockstats 975723 '["subsidy","totalfee"]' · bitcoin-cli getdifficulty

Retarget at block 975,744: progress and estimate →

It falls when difficulty rises.

Expected value at today’s difficulty, not realized revenue: luck, pool fees and power are not in it.

Calculation · mempool.space ·block 975,723 ·read 13 Nov 2026, 23:36 UTC ·Hashprice at difficulty: Full rule →

Miner’s Bench ↓

What the miners’ reward was made of

0.95%

from transaction fees, of the 454.3 BTC paid for the last 144 blocks, 975,580–975,723; the new-coin subsidy paid the rest

New-coin subsidy
99.05%
Transaction fees
0.95%

The subsidy halves at block 1,050,000, about 516 days away.

On-chain fees only: payments to pools made out of band, such as transaction accelerators, never enter the chain and are not counted.

Chain · Blocks 975,580–975,723, mempool.space ·read 13 Nov 2026, 23:36 UTC ·Hashprice at difficulty: Full rule →

Fees & blocks →

Difficulty since 2009

365days since the all-time high

the record difficulty of 155,973,032,196,071.94 was set at block 921,312 on 29 Oct 2025; counted to block 973,783, 30 Oct 2026, which was mined at 148,364,561,003,867.39

Filed by the data job; no person read it first →

Log scale · each gridline 10,000× the one below · M million, B billion, T trillion · lines mark halvings and the all-time high

Days run between block-header timestamps and are cut to whole days.

Chain · Block headers, first block of each difficulty period ·through block 973,783 ·read 30 Oct 2026 ·Difficulty: Full rule →

The stretch without a new high →
Dates, sources & limits

Halvings, by block header time: 28 Nov 2012, 9 Jul 2016, 11 May 2020, 20 Apr 2024.

All 484 periods as CSV →

Difficulty by period, the newest 52 of 484 difficulty periods, to block 973,783
PeriodFirst blockMinedDifficulty
483973,72829 Oct 2026148,364,561,003,867.39

Filed by the data job; no person read it first →

482971,71216 Oct 2026140,577,680,051,919.62

Filed by the data job; no person read it first →

481969,6963 Oct 2026132,716,002,350,731.27
480967,68019 Sep 2026132,757,073,449,487.51
479965,6645 Sep 2026127,450,789,715,843.13
478963,64823 Aug 2026125,807,076,547,197.55
477961,6328 Aug 2026127,479,855,693,691.41
476959,61625 Jul 2026126,231,507,121,868.18
475957,60011 Jul 2026127,170,500,429,035.18
474955,58427 Jun 2026133,869,853,540,305.39
473953,56814 Jun 2026124,932,866,006,548.15
472951,55229 May 2026138,955,357,012,247.29
471949,53615 May 2026136,607,070,854,775.06
470947,5202 May 2026132,472,011,079,030.51
469945,50417 Apr 2026135,594,876,535,256.58
468943,4883 Apr 2026138,966,872,071,213.20
467941,47220 Mar 2026133,793,147,307,542.74
466939,4565 Mar 2026145,042,165,424,853.28
465937,44019 Feb 2026144,398,401,518,100.94
464935,4247 Feb 2026125,864,590,119,494.26
463933,40822 Jan 2026141,668,107,417,558.24
462931,3928 Jan 2026146,472,570,619,930.76
461929,37625 Dec 2025148,258,433,855,481.31
460927,36011 Dec 2025148,195,306,640,204.70
459925,34427 Nov 2025149,301,205,959,699.89
458923,32812 Nov 2025152,271,405,447,597.37
457921,31229 Oct 2025155,973,032,196,071.94 (record)
456919,29616 Oct 2025146,716,052,770,107.46
455917,2801 Oct 2025150,839,487,445,890.49
454915,26418 Sep 2025142,342,602,928,674.92
453913,2485 Sep 2025136,039,872,848,261.31
452911,23222 Aug 2025129,699,156,960,680.89
451909,2168 Aug 2025129,435,235,580,344.81
450907,20026 Jul 2025127,620,086,886,391.78
449905,18412 Jul 2025126,271,255,279,306.99
448903,16829 Jun 2025116,958,512,019,762.11
447901,15214 Jun 2025126,411,437,451,912.23
446899,13631 May 2025126,982,285,146,989.29
445897,12017 May 2025121,658,450,774,825.00
444895,1043 May 2025119,116,256,505,723.46
443893,08819 Apr 2025123,234,387,977,050.89
442891,0725 Apr 2025121,507,793,131,898.06
441889,05623 Mar 2025113,757,508,810,853.99
440887,0409 Mar 2025112,149,504,190,349.28
439885,02423 Feb 2025110,568,428,300,952.69
438883,0089 Feb 2025114,167,270,716,407.59
437880,99227 Jan 2025108,105,433,845,147.16
436878,97612 Jan 2025110,451,907,374,649.51
435876,96029 Dec 2024109,782,075,598,905.18
434874,94416 Dec 2024108,522,647,629,298.15
433872,9282 Dec 2024103,919,634,711,492.17
432870,91218 Nov 2024102,289,407,543,323.80

Hashes a second, from a pencil to the network

26powers of ten apart

pencil and paper, 7.77 × 10⁻⁶ H/s on 28 Sep 2014; the network, about 956 EH/s on 13 Nov 2026, 23:36 UTC

Log scale: bar length counts powers of ten from 10⁻⁶ H/s
  1. The networkabout 956 EH/s

    13 Nov 2026, 23:36 UTC · estimate · 11 min 6 s to a block · mempool.space ↗

  2. Bitmain Antminer S23 Hyd580 TH/s

    announced 27 May 2025 · rated · 34.8 years to a block · Bitmain ↗

  3. Bitaxe Gamma 6011,070 GH/s

    11–17 Oct 2026 · measured · 18,800 years to a block · Satoshi Gazette

  4. Avalon batch #1 unit66 GH/s

    shipped 20 Jan 2013 · rated · 305,000 years to a block · Avalon ↗

  5. Butterfly Labs BitForce Single832 MH/s

    Dec 2011 · rated · 24.2 million years to a block · Butterfly Labs ↗

  6. ATI Radeon HD 5870, stock clock371 MH/s

    11 May 2011 · measured · 54.4 million years to a block · Phateus ↗

  7. One processor, stock client of June 2010400 kH/s

    22 Jun 2010 · stated · 50.4 billion years to a block · Satoshi Nakamoto ↗

  8. Nintendo Game Boyroughly 0.8 H/s

    27 Mar 2021 · stated · 2.52 × 10¹⁶ years to a block · stacksmashing ↗

  9. IBM 14010.0125 H/s

    23 May 2015 · extrapolated · 1.61 × 10¹⁸ years to a block · Ken Shirriff ↗

  10. Pencil and paper7.77 × 10⁻⁶ H/s

    28 Sep 2014 · extrapolated · 2.59 × 10²¹ years to a block · Ken Shirriff ↗

Times are difficulty × 2³² ÷ hashrate at the difficulty named: an average wait, not a forecast.

Calculation · The network: mempool.space, read 13 Nov 2026, 23:36 UTC ·times at the difficulty set at block 973,728 ·read 30 Oct 2026

Dates, sources & limits

Difficulty 148,364,561,003,867.39, set at block 973,728 (period 483).

Years of 365.25 days. Hashrates and times are cut to three significant figures, never rounded.

  • Pencil and paper. 0.67 hashes per day (7.77 × 10⁻⁶ H/s, derived): one SHA-256 round, timed by hand at 16 min 45 s, times the 128 rounds a mining hash needs; no whole hash was done by hand. Live page ↗ · Archived copy ↗
  • IBM 1401. 80 seconds per double SHA-256 (0.0125 H/s, derived), twice a single SHA-256 timed at about 40 s on an IBM 1401, a model announced in 1959. Bitcoin’s hash ran on one input card; no bitcoin was mined. Live page ↗
  • Nintendo Game Boy. Roughly 0.8 hashes a second, read off the screen. A PC ran the node and the miner software; the Game Boy did the hashing. Live page ↗
  • One processor, stock client of June 2010. About 400 kH/s per processor was typical, Satoshi wrote on 22 June 2010; a processor ran one mining thread. Live page ↗ · Archived copy ↗
  • ATI Radeon HD 5870, stock clock. 371 (Mhash/s, the thread’s unit) at stock clock with the phatk 1.0 kernel, a self-reported benchmark posted 11 May 2011. Archived copy ↗
  • Butterfly Labs BitForce Single. Rated 832 MH/s (±10%) at 80 W, the maker’s spec, on its product page as archived 18 Dec 2011. Archived copy ↗
  • Avalon batch #1 unit. Rated 66 GH/s per unit, the maker’s rating. Batch #1, 300 units, shipped 20 Jan 2013. Archived copy ↗ · Batch #1 ships ↗
  • Bitmain Antminer S23 Hyd. 580 TH/s typical at 5,510 W (version 580T-10), the maker’s spec, announced 27 May 2025. Live page ↗ · Archived copy ↗
  • Bitaxe Gamma 601. Median 1,070.3 GH/s at 20.74 W over 11–17 Oct 2026: 5,490 readings, AxeOS v2.13.1, 525 MHz, the editor’s unit.
  • The network. The mean of mempool.space’s last three complete UTC daily estimates, not a measured hashrate. The source’s daily series ↗
Hashrate, 3-day average: about 956 EH/s

Hashrate, 3-day average

About956EH/s

the mean of the last three complete UTC days, from how fast blocks were found

Estimate · EH/s, one point a UTC day

The 7-day mean, about 1,053 EH/s, is about 1% lower than the 7 days before it.

Not a count of machines: one day swings with luck.

Calculation · Three-day mean of mempool.space’s daily estimates ·last complete day 12 Nov 2026 ·read 13 Nov 2026, 23:36 UTC

Dates, sources & limits

Dated link to this window →The source’s daily series ↗

Hashrate, daily estimate, EH/s — 7 UTC days to 30 Oct 2026
UTC dayEH/s, about
30 Oct 20261,065
29 Oct 2026964
28 Oct 20261,011
27 Oct 20261,105
26 Oct 20261,124
25 Oct 20261,095
24 Oct 20261,007
Miner’s Bench: two setups, compared in sats

Miner’s Bench

Expected sats for two setups, not a payout; illustrative defaults.

Network & period · 365 days · block 975,723

Both setups use these inputs.

Illustrative

mempool.space · read 13 Nov 2026, 23:36 UTC

mempool.space · read 13 Nov 2026, 23:36 UTC

mempool.space · read 13 Nov 2026, 23:36 UTC

Scenario A

Scenario B

Uptime, idle power & pool fees · A: 95%, 0 W, 2% · B: 95%, 0 W, 2%

A · per day

≈ 7,966 sats a day after pool fees

79.8 kWh a day

Break-even power price: 99.8 sats/kWh

Over 365 days
Expected sats
≈ 2,907,438 sats · 0.02907438 BTC
Energy
29,127 kWh
Efficiency
17.5 J/TH

B · per day

≈ 7,966 sats a day after pool fees

68.4 kWh a day

Break-even power price: 116.4 sats/kWh

Over 365 days
Expected sats
≈ 2,907,438 sats · 0.02907438 BTC
Energy
24,966 kWh
Efficiency
15 J/TH

Difference · B minus A · per day

0 expected sats a day · +16.6 sats/kWh break-even.

What moves the result? · one change at a time

Difficulty +10%

≈ 7,241 sats a day

Break-even 90.7 sats/kWh

Change: −724 sats a day vs A

Block fees halved

≈ 7,928 sats a day

Break-even 99.3 sats/kWh

Change: −38 sats a day vs A

Power draw +10%

≈ 7,966 sats a day

Break-even 90.7 sats/kWh

Change: 0 sats a day vs A

Uptime −10 points (floor 0%)

≈ 7,127 sats a day

Break-even 99.8 sats/kWh

Change: −838 sats a day vs A

Model static-v2: expected gross BTC/day = TH/s × 10¹² × 86,400 ÷ (difficulty × 2³²) × (subsidy + fees per block) × uptime; pool fees come off the whole reward; kWh a day counts hashing watts while up and idle watts while down; break-even = expected sats a day ÷ kWh a day.

Held for the whole period: difficulty, fees per block and the starting subsidy.

Not counted: hardware, hosting, repairs, financing, taxes, insurance, cooling beyond the entered watts, curtailment credit and heat sale.

Pools

61.56% · 559 of 908 blocks in the one-week sample carried the three largest pool labels · read 11 Nov 2026

Filed by the data job; no person read it first →

Pool labels, not independent miners, ownership or a live hashrate measurement.

Pools →

Stories: Bitcoin Rallied 30 Percent This Summer. Its Hashrate Went the Other Way (3 Sep 2026) · IREN Is Leaving Bitcoin Mining for AI. The Power Does Not Leave With It (30 Aug 2026) · Mining →

Reproduce this page2 datasets: 1 committed file, 1 checksum and 5 node commands

Each download’s sha256 is printed below and in its metadata file:shasum -a 256 <file>

Commands for your own node, each beside what the committed data records, on the chain named by its block 961,632.The chain the figures describe →

  • Hashprice at difficulty

    Dataset ID sg-hashprice · method 3

    Hashprice at difficulty: Full rule →

    Live

    Read when the page loads; a response is reused for up to five minutes. Nothing is saved, so there is no file or download.

    Hashprice at difficulty: Its readings as JSON →

  • Difficulty

    Dataset ID sg-difficulty-ledger · method 1.1.0

    Difficulty: Full rule →

    Committed file
    content/data/series/epochs.json
    Dated

    As of 30 Oct 2026, 06:02 UTC · block 973,783

    On Downloads

    Difficulty, sg-difficulty-ledger.json · 347 kB

    It holds the difficulty rows of content/data/series/epochs.json alone, with the reward ledger left out and one field added from the record, filed_by: who filed each period’s row.

    Its sha256 is 0d01887d335ba21b059308c01cff3180f50510accac297218619010b468653b6

    sg-difficulty-ledger.metadata.json carries the same checksum.

    Difficulty: Its entry on Downloads →

    On your node
    1. bitcoin-cli getblockhash 973728Prints 0000000000000000000104150b08ff89bbb2d11bab42c245c82b8165ab2e2c11, the first block of difficulty period 483, the latest in the file.
    2. bitcoin-cli getblockheader 0000000000000000000104150b08ff89bbb2d11bab42c245c82b8165ab2e2c11Prints that block’s header, with bits 1701e5ac and its difficulty. The file keeps that difficulty, Bitcoin Core’s double, written out in full as 148364561003867.40625, so a node may print fewer digits; the exact value, cut to eight places, is 148364561003867.39503908.
    3. bitcoin-cli getblockhash 973783Prints 0000000000000000000093ae4ee822c8d4dab8ad40a2146aa6a073a03a00f724, the last block the file runs through.
    4. bitcoin-cli getblockhash 921312Prints 000000000000000000005def76c59fdce95a3cf277e6da4a81db0b9e1a2256d1, the first block of difficulty period 457, which set the record difficulty.
    5. bitcoin-cli getblockheader 000000000000000000005def76c59fdce95a3cf277e6da4a81db0b9e1a2256d1Prints that block’s header, with bits 1701cdfb and its difficulty; the exact value, cut to eight places, is 155973032196071.94703509.

Also on this page