What if two dashboards showed the same Bitcoin miner two very different daily revenue figures, and both were technically correct? That happens more often than most miners realize. Hashprice looks like a simple number: dollars earned per unit of hashrate per day. But behind that number sits a chain of assumptions about difficulty, fees, uptime, and units. Change one assumption and the figure moves by several percent.
That matters because hashprice is often the first number a miner checks before deciding whether to plug in another rig, sign a hosting contract, or sell forward production. If the dashboard’s methodology is unclear, the decision rests on a guess dressed up as data. This guide walks through how to compare Bitcoin hashprice dashboards in a way that holds up. It covers the formula, the hidden assumptions, the unit traps, and the practical checks that separate a reliable dashboard from a pretty chart.
Start With the Formula, Not the Chart
Every hashprice dashboard is solving roughly the same equation. Daily revenue per unit of hashrate equals block subsidy plus transaction fees, multiplied by BTC price, divided by network hashrate, adjusted for the share of blocks a given hashrate would win. The concept has been in circulation since around 2020, though the exact origin is hard to pin down.
The trouble is in the details. Providers differ on:
- Whether transaction fees are included in the revenue figure
- Whether the calculation uses live difficulty or the difficulty from the last retarget
- What pool fee assumption is baked in, if any
- Whether the number is gross revenue or net of an assumed electricity cost
- Which unit the final figure is expressed in
A dashboard that publishes its methodology page is already ahead of one that does not. When comparing two dashboards, read both methodology pages side by side and look for the same five items above. If one provider does not state its fee assumption, treat its hashprice as an estimate, not a benchmark.
This is the same discipline that pays off when you compare CRM tools by which features actually matter: the spec sheet is less important than the assumptions behind it.
The Difficulty Question: Live Versus Last Retarget

Bitcoin retargets its mining difficulty every 2,016 blocks, which works out to roughly two weeks. Between retargets, the network’s actual difficulty is fixed, but the hashrate estimate moves constantly as blocks arrive faster or slower than the ten-minute target.
Here is where dashboards diverge. Some compute hashprice using the difficulty in force right now. Others use the difficulty from the most recent retarget, which is the same thing until the next adjustment. A third group uses a smoothed or projected difficulty, anticipating where the network is heading.
None of these is wrong. But they produce different numbers on the same day, especially in the days right before a large adjustment. If a miner is modeling a 30-day contract, a dashboard using live difficulty will show more volatility than one using a smoothed projection. Know which you are looking at before drawing conclusions.
A practical check: pull the hashprice from two dashboards on the same day and compare. If the gap is larger than a couple of percent, one of them is likely using a different difficulty basis, a different fee assumption, or both. That gap is your clue to dig into the methodology.
Units Are a Silent Source of 1,000x Errors
This is the mistake that catches experienced people, not beginners. Some dashboards quote hashprice in USD per terahash per day (USD/TH/s/day). Others quote USD per petahash per day (USD/PH/s/day). One petahash equals one thousand terahashes. Mix the two and you are off by a factor of 1,000.
The error usually shows up in a spreadsheet. Someone copies a figure from Dashboard A, pastes it next to a figure from Dashboard B, and builds a model on numbers that are three orders of magnitude apart. The model looks fine. The conclusion is nonsense.
Before comparing any two dashboards, write down the unit each one uses. Then convert everything to a single unit before doing any arithmetic. Most providers state their unit clearly in the chart axis or the methodology page, but not all do. If a dashboard does not state its unit, that is a red flag worth noting.
Transaction Fees: Small Line Item, Big Comparability Problem
Transaction fees are the wildcard in hashprice. Fees as a share of total miner revenue swing widely. In quiet periods they can sit in the low single digits. During congestion they can climb into double digits. That swing changes the hashprice figure meaningfully depending on whether fees are counted.
A dashboard that includes fees will show a higher hashprice than one that does not, and the gap widens exactly when the network is busiest. That is inconvenient, because busy periods are precisely when miners are watching revenue most closely.
The fix is not to pick one convention and declare it correct. The fix is to compare like with like. If Dashboard A includes fees and Dashboard B excludes them, either find a fee-inclusive figure from both or accept that the two numbers are measuring different things. A miner building a revenue forecast should generally use the fee-inclusive number, because fees are real revenue. A miner benchmarking hardware efficiency might prefer the subsidy-only figure for stability. Both are legitimate, as long as the choice is deliberate.
The Halving Shadow and Backfilled History
The April 2024 halving cut the block subsidy from 6.25 to 3.125 BTC. That is a structural, permanent reduction in hashprice. Any dashboard that shows historical hashprice has to decide how to handle that break.
Some dashboards backfill history using the subsidy that applied at the time, which is the honest approach. Others recalculate history using current parameters, which produces a smooth line that never existed. A third group simply truncates history at the halving.
When comparing dashboards, look at how each one handles the halving boundary. If a chart shows a continuous line across April 2024 with no visible step down, ask why. The subsidy halved. The hashprice should show it. A dashboard that smooths over a real structural change is telling a story, not reporting data.
The same logic applies to any future halving. Build the habit now of checking whether a dashboard’s history is point-in-time or recalculated.
Gross Revenue Versus Net of Power Costs
Hashprice is usually a gross revenue figure: what a unit of hashrate earns before you pay for electricity. But some dashboards go further and show a net figure, subtracting an assumed power cost per kilowatt-hour.
These are different metrics and they answer different questions. Gross hashprice tells you what the network pays. Net hashprice tells you what a specific operation keeps, and it depends entirely on the power cost assumption the dashboard chose. A dashboard assuming four cents per kWh will show a very different net figure than one assuming eight cents.
For comparing dashboards, use gross hashprice as the common denominator. It is the same for every miner, regardless of where they plug in. Then apply your own power cost separately. If a dashboard only offers a net figure, find out what power cost it assumes before you trust it, and be aware that the assumption may not match your situation at all.
This separation of concerns is the same principle that makes any tool comparison cleaner. It is why a careful buyer will compare AI coding tools by their actual features before committing rather than judging on a single headline number. (Ai music tools features compare before you commit)
A Practical Comparison Checklist
When two dashboards disagree, work through the following in order. It usually takes less than ten minutes and resolves most discrepancies.
- Confirm the unit. USD/TH/s/day versus USD/PH/s/day. Convert both to the same unit first.
- Check the fee treatment. Does each dashboard include transaction fees or not?
- Identify the difficulty basis. Live, last retarget, or smoothed projection?
- Look at the timestamp. Are both figures from the same moment, or is one an hour stale?
- Read the methodology page. If there is none, downgrade the dashboard’s reliability.
- Check the halving handling. Does historical data reflect the actual subsidy at the time?
- Confirm gross versus net. Is a power cost assumption baked in?
Run this checklist on any dashboard before you rely on it for a decision. The exercise is boring, and that is the point. Boring checks prevent expensive mistakes.
What Actually Works in Practice
A few habits separate miners who use hashprice well from those who get burned by it.
First, pick one dashboard as your primary source and use it consistently. Switching between dashboards mid-analysis introduces methodology noise that looks like market movement. Consistency beats theoretical accuracy when you are tracking a trend.
Second, keep a second dashboard as a cross-check, but only for spotting anomalies. If your primary source suddenly diverges from the secondary by more than a few percent, something changed: a methodology update, a data outage, or a genuine market shift. Investigate rather than assume.
Third, record the methodology assumptions alongside any figure you save. A spreadsheet cell that says “hashprice: 0.055” is useless six months later if you cannot remember whether fees were included. A cell that says “0.055 USD/TH/s/day, fees included, live difficulty” is a data point you can actually use.
Fourth, do not treat hashprice as a forecast. It is a snapshot of current conditions. Difficulty adjusts, fees move, and price swings. Any model that projects hashprice forward without accounting for those variables is guessing with extra steps.
The same discipline applies across tool categories. Teams that compare social media management tools by their publishing workflow learn quickly that the feature that matters is the one baked into daily use, not the one on the marketing page. Hashprice dashboards reward the same skepticism.
Where Dashboards Fit in a Broader Tool Stack
Hashprice is one input among many. Miners also track pipeline economics, contract terms, and operational costs. Some of the same comparison instincts carry over: check the assumptions, confirm the units, and read the methodology before trusting the output. If you are evaluating sales or operations software alongside your mining stack, the same logic applies when you compare pipeline management tools across sales workflows. The tool is only as good as the assumptions it hides. (Ai coding tools features compare before you commit)
Conclusion
Comparing Bitcoin hashprice dashboards is less about finding the “right” number and more about understanding what each number actually measures. The formula is simple. The assumptions behind it are not. Unit conventions, fee treatment, difficulty basis, halving handling, and gross versus net all shift the figure, sometimes by several percent and occasionally by a factor of a thousand.
The miners who get this right are not the ones with the most sophisticated models. They are the ones who read the methodology page, convert their units, and keep their assumptions written down. That is a low bar, and clearing it puts you ahead of most of the market. Pick a primary dashboard, cross-check with a second, document what you are looking at, and treat every hashprice figure as an estimate with a stated basis rather than a fact. Do that, and the numbers start working for you instead of against you.
Frequently Asked Questions
What exactly does hashprice measure?
Hashprice measures the expected daily revenue per unit of hashrate, usually expressed as dollars per terahash or petahash per day. It combines block subsidy, transaction fees, BTC price, and network hashrate into a single figure. Because it depends on several moving inputs, different dashboards can report different values for the same moment.
Why do two hashprice dashboards show different numbers on the same day?
The most common reasons are differences in whether transaction fees are included, whether the calculation uses live difficulty or the last retarget difficulty, and whether the figure is gross revenue or net of an assumed power cost. Unit differences between terahash and petahash can also create large gaps if one figure is converted incorrectly.
Is hashprice quoted per terahash or per petahash?
Both conventions exist. Some dashboards use USD per terahash per day, others use USD per petahash per day. Since one petahash equals one thousand terahashes, mixing the two produces errors of 1,000x. Always confirm the unit before comparing figures from different sources.
Should hashprice include transaction fees?
There is no single correct answer, but consistency matters more than the choice. Fee-inclusive hashprice reflects real revenue and is better for forecasting. Subsidy-only hashprice is more stable and useful for benchmarking hardware efficiency. The key is to compare fee-inclusive figures with fee-inclusive figures, never mixing the two.
How does the Bitcoin halving affect hashprice comparisons?
The April 2024 halving cut the block subsidy from 6.25 to 3.125 BTC, which structurally lowered hashprice. Dashboards differ in how they handle historical data around that date. Some backfill using the subsidy in force at the time, which is accurate. Others recalculate history with current parameters, which produces a smoother line than reality. Check which approach a dashboard uses before trusting its historical charts.
How often should hashprice dashboards be cross-checked?
A monthly cross-check is usually enough for trend tracking, plus an immediate check whenever a dashboard shows an unexpected jump or drop. If two dashboards diverge by more than a few percent, investigate the methodology before acting on either figure. Frequent switching between sources introduces noise that can look like market movement when it is really just a change in assumptions.