Hashrate is the rate at which a computer or group of computers performs cryptographic hash calculations. In Bitcoin mining, it measures how many SHA-256d hash attempts are made per second while miners search for a block header whose hash is below the network target. Hashrate measures proof-of-work computation; by itself, it does not measure transaction throughput, block capacity, or mining profitability.
Bitcoin's estimated network hashrate was about 859.9 EH/s on August 26, 2026. Because network hashrate cannot be measured directly across every active miner, figures like this are estimates derived from observed block production and network difficulty.
What does hashrate mean?
A hash function converts input data into a fixed-length output. Bitcoin uses double SHA-256, often written as SHA-256d, in its proof-of-work process. Mining hardware repeatedly hashes candidate block headers while changing fields such as the nonce and extranonce-related data. A block is valid only when the resulting hash is numerically lower than the target set by the protocol.
Each hash attempt is effectively independent. A miner cannot predict which attempt will produce a valid result, so mining consists of repeated trials at very high speed. A machine rated at 200 TH/s performs about 200 trillion hash attempts per second under its operating conditions.
The standard units are:
- 1 kH/s = 1,000 hashes per second
- 1 MH/s = 1 million H/s
- 1 GH/s = 1 billion H/s
- 1 TH/s = 1 trillion H/s
- 1 PH/s = 1 quadrillion H/s
- 1 EH/s = 1 quintillion H/s
- 1 ZH/s = 1 sextillion H/s, or 1,000 EH/s
Bitcoin mining has progressed from CPU and GPU mining to specialized ASIC hardware operating at terahash and petahash scales, while the global network now operates at hundreds of exahashes per second. Public network-hashrate charts should always be read as estimates rather than a direct count of every active ASIC.
How hashrate works in Bitcoin proof of work
Bitcoin proof of work makes block production computationally expensive while keeping block verification comparatively straightforward. A miner works on a candidate block and repeatedly hashes its header. When a miner finds a hash below the network target, it can submit the completed block to the network, where full nodes independently verify that the block follows Bitcoin's consensus rules.
More hashrate increases a miner's probability of finding a valid block over time, but it does not guarantee a specific short-term result. If a miner contributes 1% of the network's total hashrate over a sufficiently long period, its expected share of block discoveries is roughly 1%. Actual results can vary considerably over shorter periods because block discovery is probabilistic.
This variance is one reason many miners use mining pools. Instead of waiting for an individual miner to find a full block, pools track contributed work through shares and distribute rewards according to the pool's payout method.
Hashrate is also related to the amount of proof of work accumulated by the blockchain. When competing valid branches appear temporarily, Bitcoin nodes ultimately follow the chain with the most accumulated proof of work under the protocol's chain-selection rules.
Hashrate and mining difficulty
Hashrate and difficulty are closely related, but they measure different things. Hashrate is the rate of hash attempts. Difficulty expresses how hard it is, on average, to find a block that meets Bitcoin's current network target.
Bitcoin adjusts difficulty every 2,016 blocks, with the aim of keeping average block production near one block every 10 minutes. When total network hashrate rises and blocks are found faster than expected, difficulty will generally rise at the next adjustment. When hashrate falls and blocks are found more slowly, difficulty can decline.
At the difficulty period beginning with block 963,648, Bitcoin difficulty was approximately 125.81 trillion on August 26, 2026. At that difficulty, the expected amount of work required to find one valid block was about 5.403 × 10²³ hash attempts. This is a statistical expectation, not a fixed number of attempts required for every block.
This is why a sustained rise in network hashrate does not permanently make Bitcoin blocks arrive faster. Before the next difficulty adjustment, blocks may be found more quickly, but the adjustment mechanism responds to changes in aggregate mining power.
Local, pool, and network hashrate
Miners commonly encounter several different hashrate figures, and they should not be expected to match exactly.
- Local hashrate: The hashrate reported by an ASIC or mining management system. It is based on the miner's own measurements and may be calculated over relatively short time windows.
- Pool hashrate: The pool's estimate of the hashrate contributed by a miner, worker, account, or the pool as a whole. It is calculated from shares received over a given reporting window.
- Network hashrate: An estimate of the total hashpower competing to mine Bitcoin blocks across the network. It is inferred from block production and difficulty because no single observer can directly measure every active miner.
A miner's local hashrate and the pool's reported hashrate can differ for several reasons. They may use different averaging windows, and the pool can only estimate hashrate from the shares it receives. Short-term statistical variance, stale or rejected shares, connectivity interruptions, downtime, thermal throttling, and unstable hardware can all contribute to a persistent difference.
ViaBTC explains that its real-time pool hashrate uses an approximately 10-minute average, while a mining machine may use a shorter and more variable reporting interval. For this reason, operators should compare measurements over a meaningful period instead of treating every short-term difference as a fault.
Network hashrate requires a different interpretation. It is not reported directly by all miners to a central system. Services such as Blockchain.com and Mempool.space estimate it from recent block production and current difficulty. Short observation windows can fluctuate because block intervals are random; longer windows are smoother but react more slowly to real changes in network hashrate.
Why hashrate matters
Security
More aggregate honest hashrate generally increases the amount of computing power required to sustain a majority-hashpower attack on Bitcoin. An attacker attempting to reorganize recent transaction history would need to control or obtain a very large amount of mining power relative to the rest of the network.
Total hashrate, however, is not a complete measure of decentralization. The distribution of hashpower among pools and operators, geographic concentration, access to ASIC hardware, energy supply, and the role of full nodes in enforcing consensus rules also matter.
Mining probability and revenue
For an individual miner, hashrate is a primary input into expected mining output. More hashrate means more opportunities to find valid shares in a pool and, statistically, a larger expected share of mining rewards.
Profitability depends on much more than hashrate alone. Important variables include network difficulty, block subsidy, transaction fees, Bitcoin price, electricity cost, ASIC efficiency, uptime, hosting expenses, pool fees, and financing costs. Since the fourth Bitcoin halving at block 840,000 in April 2024, the block subsidy has been 3.125 BTC per block.
Industrial mining data illustrate the difference between hashrate and profitability. MARA reported 70.3 EH/s of energized hashrate and 2,422 BTC mined in Q2 2026, while also reporting a purchased-energy cost of $38,690 per BTC at owned sites. The same amount of hashrate can produce very different economic results depending on power price, equipment efficiency, uptime, and other operating conditions.
Hashrate, electricity, and ASIC efficiency
Hashrate requires electricity, but hashrate is not a measure of energy consumption. ASIC efficiency is commonly expressed in joules per terahash (J/TH). A lower J/TH value means the miner requires less energy to perform the same number of hash attempts.
For example, two miners can produce the same 200 TH/s while drawing different amounts of power. The more efficient machine will generally have a lower operating cost at the same electricity price. Facility overhead such as cooling, transformers, pumps, and networking also contributes to total site power consumption.
The Cambridge Bitcoin Electricity Consumption Index estimated Bitcoin power demand at 16.09 GW and annualised electricity consumption at 141.02 TWh/year on August 1, 2026, with a modeled range rather than a directly metered global total. Estimates of Bitcoin energy use depend on assumptions about network hashrate, hardware efficiency, electricity economics, and facility overhead.
For miners, the practical relationship is simple: hashrate describes computing output, while J/TH describes how efficiently mining hardware produces that hashrate. Profitability then depends on how those technical figures interact with electricity price, network difficulty, mining rewards, uptime, and other operating costs.
Practical implications for miners
Hashrate should be evaluated together with other operating data rather than treated as a standalone specification. A miner can report high local hashrate while still underperforming at the pool because of rejected shares, unstable connectivity, downtime, or hardware errors.
A useful operating view separates three layers:
- ASIC-side metrics: local hashrate, power consumption, temperatures, fan or pump performance, and hardware errors.
- Pool-side metrics: pool-reported hashrate, accepted shares, stale and rejected shares, rejection rate, and connection stability.
- Mining economics: BTC earned over time, payout-method effects, transaction-fee rewards, electricity cost, pool fees, and other operating expenses.
Before deploying equipment, estimate expected results using hashrate, network difficulty, power consumption, electricity price, and pool fees. The ViaBTC Mining Profitability Calculator can help with scenario analysis, but calculator results should be treated as estimates because difficulty, fees, uptime, and market prices can change.
When a miner's local hashrate and pool-side hashrate differ persistently, check the reporting windows first. If the difference remains large over time, investigate rejected or stale shares, network stability, miner temperature, firmware, and hardware condition.
FAQ
Is hashrate the same as transaction speed?
No. Hashrate measures proof-of-work hash attempts per second. Bitcoin transaction throughput depends on factors such as block space, transaction size, demand for block space, fee conditions, and higher-layer payment systems. Increasing hashrate does not directly increase the number of transactions that fit into a block.
Why does Bitcoin network hashrate change?
Miners bring machines online, shut them down, upgrade hardware, overclock or underclock equipment, relocate operations, or curtail in response to revenue, difficulty, electricity prices, weather, and grid conditions. Public network-hashrate estimates also contain short-term statistical noise because they are inferred from block production rather than directly measured.
Does higher hashrate always mean Bitcoin is more decentralized?
No. Higher hashrate generally increases the amount of computing power required for a sustained majority-hashpower attack, but it does not show how evenly that hashrate is distributed among pools, operators, regions, or hardware suppliers.
Why is pool hashrate lower than ASIC hashrate?
The two figures may use different time windows, and a pool estimates hashrate from the shares it receives. Stale or rejected shares, network interruptions, downtime, thermal throttling, and unstable hardware can also contribute to a persistent difference between pool-side and local readings.
References
- Bitcoin White Paper — Bitcoin proof of work and chain selection.
- Bitcoin Developer Guide: Block Chain — Proof of work, difficulty adjustment, and chain behavior.
- Bitcoin Developer Guide: Mining — Mining workflow, targets, shares, and pooled mining.
- Bitcoin Core RPC: getdifficulty — Bitcoin difficulty definition.
- Mempool.space Mining Hashrate API — Network hashrate and difficulty data.
- Blockchain.com Hash Rate Chart — Bitcoin network-hashrate estimates.
- ViaBTC Help Center: Why is the Hashrate Shown in the Mining Pool Lower than that of the Mining Machine? — Pool and miner hashrate differences.
- ViaBTC Help Center: How to Stabilize the Hashrate? — Operational guidance for hashrate stability.
- ViaBTC Hashrate Help Center — Related ViaBTC support resources.
- ViaBTC Mining Profitability Calculator — Mining profitability estimates.
- MARA Q2 2026 Shareholder Letter — Energized hashrate, BTC production, and energy-cost data.
- Cambridge Bitcoin Electricity Consumption Index — Estimated Bitcoin power demand and annualised electricity consumption.
- CBECI Methodology — Methodology and assumptions behind Bitcoin electricity estimates.