Costs & economics
Hashrate Explained: TH/s, PH/s and EH/s for Bitcoin Mining
TH/s means terahashes per second: one trillion hash calculations each second. PH/s and EH/s describe larger rates. Hashrate measures computational work rate, not a Bitcoin balance or a guaranteed payout. Reading these units correctly helps you compare mining quotes, capacity announcements and pool reports.
What a hash rate measures
Bitcoin miners repeatedly hash candidate block headers, looking for a result that meets the network target. More hashes per second mean more attempts over a given period. The network's target and the rewards associated with successful blocks determine how those attempts translate into expected revenue. Bitcoin developer guide to mining.
The final /s matters. A hash is a computation; hashes per second is a rate. Running 10 TH/s for one second and running 10 TH/s for one day have the same rate but perform very different amounts of work. Mining rental quotes therefore need both rate and duration.
Do not read TH/s as tokens per second or coins per day. It is also algorithm-specific. A Bitcoin SHA-256 rate cannot be compared directly with a similarly numbered rate for an unrelated mining algorithm. Begin a quote comparison by checking that the computation being supplied is the computation your selected pool accepts.
Convert between TH/s, PH/s and EH/s
The prefixes are decimal. Tera means 10^12, peta means 10^15 and exa means 10^18, following the NIST SI prefix table. Each step from TH/s to PH/s to EH/s is a factor of 1,000.
| Rate | Hashes per second | Equivalent in TH/s |
|---|---|---|
| 1 TH/s | 10^12 | 1 |
| 1 PH/s | 10^15 | 1,000 |
| 1 EH/s | 10^18 | 1,000,000 |
For worked conversions, 0.25 PH/s × 1,000 equals 250 TH/s. Conversely, 75 TH/s ÷ 1,000 equals 0.075 PH/s. A rate of 2.4 EH/s equals 2,400 PH/s or 2,400,000 TH/s.
When converting a price, convert its denominator too. An illustrative $40 per PH/s-day is $40 ÷ 1,000 = $0.04 per TH/s-day. For 250 TH/s over two days, that gives 250 × 2 × $0.04 = $20. These are arithmetic examples, not current price quotes.
Keep fleet capacity separate from a customer's position
Think of three different records: the provider's total capacity, the portion calculated or assigned to a customer, and the work the customer's pool actually accepts. The same unit can appear on all three, but it describes a different scope each time.
S23's published pool capacity is 1 PH/s, equivalent to 1,000 TH/s. The deployment page divides that published capacity by active tokens to calculate a proportional share. The fleet figure is not the allocation of every token or every wallet.
For an illustrative 500 active tokens, the model gives 1,000 ÷ 500 = 2 TH/s per active token. A position containing 20 of those tokens has a calculated share of 40 TH/s. If another 500 tokens become active while capacity stays unchanged, the total becomes 1,000 active tokens and the calculated share falls to 1 TH/s per token. This changing share is why capacity and participation should be displayed together.
Read observed hashrate with its averaging interval
A machine or provider can report a rate while a pool estimates accepted hashrate from submitted work. Short observations can differ from longer averages. Always preserve the measurement basis, start and end times, timezone and unit before comparing reports.
Braiins' monitoring documentation, for example, exposes daily hashrate records with an explicit unit and a 24-hour average field. That is a useful model for an evidence record: a number accompanied by its unit and period. Braiins pool monitoring documentation.
As a simple exercise, suppose a position delivers 100 TH/s for 12 hours and zero for the next 12. Its full-day average is 50 TH/s, and its delivered work is 50 TH/s-days. A screenshot from the working half of the day could show 100 TH/s without describing the full day. Once you use the 50 TH/s daily average, do not halve it again for downtime.
Convert a rate into an estimate, then verify delivery
To estimate gross revenue from a hashprice, multiply the compatible hashrate, runtime and revenue rate. At an assumed $0.05 per TH/s-day, 40 TH/s for ten full days gives 40 × 10 × $0.05 = $20 gross. A larger TH/s figure does not itself establish profit because acquisition, service and operating costs are still missing.
For S23, a calculated share based on published pool capacity should remain labeled as calculated until reconciled with accepted work. The current staking program, provider allocation and pool payout records each answer a different question. Token ownership and active deployment are also distinct states.
Use the calculator guide for a complete unit-checked example and the S23 walkthrough for the ownership and deployment sequence. The hashrate rental guide explains how rates and durations become a purchased service.
Sources and further reading
- NIST: Metric SI Prefixes
- Bitcoin developer guide: Mining
- Braiins pool monitoring documentation
- S23 deployment page
Sources checked 21 September 2026. Product conditions and external documentation can change. About these guides.