Convert hashrate
Convert hashrate between all units, and see at once what your number is worth on the real network.
Your hashrate
Calculated with the network difficulty as of 30 October 2026 at 05:33 UTC: 148.36 T (source: mempool.space, updated every quarter of an hour).
In every unit
Enter a hashrate.
Where your number sits
Real devices, for comparison: the hashrate at the default setting as stated by the manufacturer, checked on 29 October 2026. Each name links to its source.
| Model | Hashrate | Share | Block, on average |
|---|---|---|---|
| Bitaxe Gamma | 1.2 TH/s | 1.130 × 10^−7% | 16,827 years |
| NerdQaxe++ | 4.8 TH/s | 4.520 × 10^−7% | 4,207 years |
| NerdQX | 6 TH/s | 5.650 × 10^−7% | 3,365 years |
| Avalon Mini 3 | 37.5 TH/s | 3.531 × 10^−6% | 538 years |
| Antminer S21+ Hydro | 395 TH/s | 3.719 × 10^−5% | 51 years |
| Antminer S21 XP Hydro | 473 TH/s | 4.454 × 10^−5% | 43 years |
The trap almost everyone falls into
Hashrate counts in powers of a thousand, not of 1,024. One TH/s is exactly one trillion hashes per second — 10¹² — and not 2⁴⁰ as with a terabyte in Windows. Anyone using the binary ladder is off by almost ten percent, and that gap grows with every step up.
This is not nitpicking. Check a pool payout with 2⁴⁰ instead of 10¹² and your result is structurally wrong, so you go looking for the mistake in the wrong place.
Why values are rounded
Above nine quadrillion, an ordinary number in JavaScript loses precision. One ZH/s is a thousand times larger than that. This page therefore calculates with decimal numbers and shows significant figures instead of a row of zeros that would be wrong anyway.