Hash rate explained: nobody counts the pickaxes, they count the gold and work backwards
Hash rate is how many guesses per second all Bitcoin miners make together. Nobody can count it directly: it is estimated from the difficulty and how fast blocks actually arrive, so every published figure is an estimate with plenty of luck in it.
Imagine trying to count every pickaxe in a gold rush valley. Men come and go, claims are hidden in side canyons, nobody fills in a form. You could never do it.
But you could stand at the assay office and weigh the gold coming in. If you know roughly how much digging it takes to find an ounce, the weight tells you how many men must be out there.
That is how Bitcoin's hash rate is measured. Nobody counts the machines. The network's speed is worked out backwards from how hard blocks are to find and how fast they arrive. Every hash rate figure you see is an estimate, and some days it is a rough one.
What it is
Hash rate is the number of guesses per second that all miners together make while searching for the next block. Each guess is one hash of a block header. The numbers are large, so they come in units: a terahash is a trillion (10 to the power 12) hashes, a petahash a thousand terahashes, an exahash a million terahashes (10 to the power 18). Network hash rate is usually given in exahashes per second, EH/s.
Miners don't report their speed to anyone, and nothing in a block records it. Bitcoin Core's own tool for this, getnetworkhashps, says so in its description: "Returns the estimated network hashes per second based on the last n blocks", with 120 blocks as the default (mining.cpp).
How it works: from one block's difficulty to a hash rate
The formula has three parts.
- Difficulty. Each block carries a target, and from it a difficulty. On average, a block at difficulty D takes D times 2 to the power 32 hashes to find. Two to the power 32 is 4,294,967,296, about 4.3 billion, the average number of guesses at the lowest possible difficulty, difficulty 1.
- Time. Bitcoin aims at one block every 600 seconds (chainparams.cpp).
- Divide. Hashes per block divided by seconds per block gives hashes per second.
Now the real numbers. Block 975,744, mined on 14 November 2026 at 05:02:50 UTC, started a new difficulty period at 134,823,837,323,272.66 (mempool.space).
- Hashes per block: 134,823,837,323,272.66 x 4,294,967,296 = about 5.79 x 10 to the power 23.
- Divided by 600 seconds: about 9.65 x 10 to the power 20 hashes per second.
- That is about 965 EH/s.
So the difficulty set at block 975,744 is what you would expect if miners together made roughly 965 quintillion guesses a second, and blocks came every ten minutes.
A cross-check from the period before. Between blocks 973,728 and 975,743, difficulty was 148,364,561,003,867 but blocks came every 11.01 minutes on average, not 10 (mempool.space). Plug 660.6 seconds into the formula instead of 600 and you get about 965 EH/s again. That is exactly why the difficulty fell by 9.13%: it was set for more pickaxes than turned up.
Now compare what an explorer shows. Read on 19 November 2026, mempool.space put the network at 1,001.75 EH/s. Its daily estimates for 15, 16, 17 and 18 November 2026 were 925.8, 1,147.5, 1,102.3 and 1,009.8 EH/s (mempool.space). The highest of those four days is 24% above the lowest. Miners didn't plug in a quarter more machines one day and unplug them two days later. Blocks simply arrived faster on some days, by luck, and the estimate followed.
Why it matters
- It's the security meter. To rewrite recent blocks, an attacker would need to outdig the rest of the network. The higher the hash rate, the more machines and power that takes. "The 51% attack explained" has the details.
- It sets the difficulty. When hash rate grows, blocks come faster and the next retarget makes the search harder, as "Mining difficulty explained" shows.
- It sets each miner's slice. A miner's expected share of blocks is its own hash rate divided by the network's. More competition means a smaller slice of the same 144 or so blocks a day. What that slice is worth is in "What miners earn: block reward plus fees".
- Who uses it. Pools, analysts and the shovel sellers all quote it. A rising hash rate makes a fine sales slide for machine sellers. The same number shrinks every buyer's share of the blocks.
Where people get it wrong
- "Hash rate is measured." It is estimated from difficulty and block times. Different sites using different windows will show different numbers for the same day.
- "Hash rate jumped 20% overnight." Over one day, around 144 blocks, luck alone moves the estimate a lot. Look at weeks, not days.
- "Hash rate tells you how many miners there are." It tells you how many guesses, not how many people or machines. One large farm and a thousand small rigs can produce the same figure.
- "A higher hash rate makes transactions faster." The difficulty adjusts to keep blocks near ten minutes, whatever the hash rate.
- "Hash rate follows the price." In the code, hash rate is linked only to difficulty and block times. Any link to the price runs through miners' own business decisions, and the formula above doesn't contain a price at all.
Do the estimate yourself
Open a block explorer and find the difficulty of the last block on the chain. Multiply it by 4,294,967,296, divide by 600, then divide by 10 to the power 18. That's the network's hash rate in EH/s at ten-minute blocks, from the same formula the professionals use.
Then look at any "hash rate record" headline in the saloon. You now know it was an estimate, of luck, divided by ten minutes.
Frequently asked questions
What is hash rate in Bitcoin?
Hash rate is the number of guesses per second that all Bitcoin miners make together while searching for a valid block. It is usually given in exahashes per second (EH/s), where one exahash is 10 to the power 18 hashes.
How is Bitcoin's hash rate calculated?
It is estimated, not counted. Take the difficulty, multiply by 2 to the power 32 to get the average number of hashes per block, and divide by the average time between blocks. Explorers do this over a window of recent blocks.
Why do hash rate figures differ between websites?
Because each site estimates from a different window of blocks, such as one day, three days or a week. Short windows swing more, because block times vary by luck.
What was Bitcoin's hash rate in November 2026?
Read on 19 November 2026, the mempool.space explorer estimated about 1,002 EH/s. The difficulty set at block 975,744 on 14 November 2026 matches about 965 EH/s at ten-minute blocks.
Does a higher hash rate make Bitcoin more secure?
Yes, in the sense that rewriting recent blocks needs more computing power and energy. It doesn't change how fast transactions confirm, because difficulty adjusts to keep blocks near ten minutes.
Sources
- mempool.space API, blocks 975,730 to 975,744 (14 November 2026)
- mempool.space API, hash rate and difficulty, one month (read 19 November 2026)
- mempool.space API, difficulty adjustments November 2025 to November 2026 (read 19 November 2026)
- Bitcoin Core source code, src/rpc/mining.cpp (getnetworkhashps)
- Bitcoin Core source code, src/kernel/chainparams.cpp (nPowTargetSpacing)

