The two numbers being compared
Market Value to Realized Value (MVRV) starts from a simple question: is the network, in aggregate, sitting on a profit or a loss right now?
Market Value is the number you already know — current price times circulating supply. Same thing as market cap. Nothing new here.
Realized Value is the interesting part. Instead of valuing every coin at today's price, it values each coin at the price it last moved on-chain. Sum that across the whole supply and you get an estimate of the network's aggregate cost basis — what the average holder actually paid, weighted by how much of the supply they hold.
MVRV is just Market Value divided by Realized Value. That's the entire formula. The mechanics are boring; the interpretation is where it gets useful.
What "last moved on-chain" actually captures
Every time a coin changes wallets, the chain records it, and that becomes the coin's new reference price for Realized Value purposes. A coin bought in 2021 and never touched since is still valued at its 2021 price in this calculation, even if the market price has tripled or fallen by half. A coin that moved last week is valued at last week's price.
The effect: Realized Value behaves like a slow-moving, supply-weighted average cost basis for the entire market. It doesn't react to daily price swings the way market cap does, because most of the supply isn't moving on any given day. Only the portion of coins that actually change hands updates the number.
This is also exactly where the metric's blunt edges live, covered below.
Reading the ratio
- MVRV > 1: the network as a whole holds unrealized profit. The higher above 1, the larger that aggregate cushion.
- MVRV = 1: current price equals the aggregate cost basis. Breakeven for the average dollar invested, in aggregate terms.
- MVRV < 1: the network as a whole is underwater. Most recently-active coins are worth less now than when they last moved.
None of this tells you what any individual holder paid. It's an aggregate. Someone who bought at $10,000 and someone who bought at $70,000 average out into one number that describes neither of them precisely. The value of MVRV is in the aggregate behavior it implies, not in describing any single participant.
Why extremes cluster at cycle turns
The logic connecting MVRV to cycle tops and bottoms isn't mystical — it's an incentive argument.
When MVRV is very high, a large share of the supply is sitting on a large unrealized gain. Historically, elevated MVRV readings have clustered near cycle tops, because a market full of holders sitting on large paper profits is a market with a large pool of people who have strong reason to sell. Not all of them do at once, but the aggregate selling pressure available at those levels is structurally higher than at other points in the cycle. Distribution from long-term holders into a rally has repeatedly coincided with these stretched readings.
At the other end, MVRV near or below 1 has historically marked stretches that are hard to sustain. When the average dollar invested in the network is at a loss, the aggregate incentive to sell weakens — people are more reluctant to realize losses than gains, a well-documented behavioral pattern that shows up in on-chain data as reduced sell pressure from underwater cohorts. Historically, prices have not spent long periods deeply below MVRV = 1 without a subsequent recovery, though "not spent long periods" is doing a lot of work in that sentence and is not a promise about any particular cycle.
Neither of these is a law of physics. They're historically observed tendencies in a market that has gone through a handful of full cycles — a sample size that should keep anyone humble about extrapolating forward.
MVRV Z-score: normalizing for the ratio's own drift
Raw MVRV has a problem: its typical range isn't stable over time. As a network matures and market cap grows into the trillions (from, hypothetically, single-digit billions years earlier), the statistical behavior of MVRV shifts too — the deviations get compressed in percentage terms even when the underlying dynamic is the same. Comparing an MVRV reading from an early, thinly-traded period to one from a mature, deep-liquidity period isn't quite apples to apples.
MVRV Z-score addresses this by normalizing:
Z-score = (Market Value − Realized Value) / standard deviation of Market Value
Instead of a raw ratio, you get a measure of how many standard deviations market value is from realized value, using the market's own historical volatility as the yardstick. A Z-score reading near a historical extreme means something closer to "this is unusual relative to this network's own history," which is a more honest claim than "MVRV is 3.5" — a number that means something different depending on what year it's from.
The tradeoff is that Z-score is a step more abstract and requires a longer price history to compute meaningfully, which is part of why raw MVRV still gets quoted more often in casual discussion even though Z-score is the more careful version.
Where the metric is blunt
Realized Value treats every on-chain movement the same way, and that's a real limitation, not a footnote.
- A sale and a wallet reshuffle look identical. Moving coins from a hot wallet to cold storage, consolidating UTXOs, or shifting between two wallets you own all update the "last moved" price, exactly like an actual sale to a new owner would. None of those events involved anyone buying or selling anything.
- Exchange-internal transfers muddy the picture further. Coins moving between an exchange's hot and cold wallets, or between omnibus accounts, can register as on-chain movement without any change in economic ownership at all.
- Lost coins never get removed from the calculation. Coins sent to inaccessible wallets, burned by lost keys, or otherwise gone forever still count toward supply and still carry whatever price they last moved at, even though nobody will ever sell them at a loss or profit. Over a long enough timeframe this is not a trivial slice of supply for older networks.
None of these break the metric outright, but they mean Realized Value is a proxy for aggregate cost basis, not a precise ledger of it. The proxy is good enough to be useful at a macro level; it is not good enough to justify treating any specific reading as a precise threshold.
How to actually use it
MVRV is a slow-moving structural gauge, not an entry or exit signal. It changes over weeks and months, not hours, because it's built from aggregate on-chain behavior that itself changes slowly. Treating a specific MVRV level as a trade trigger — "sell when it crosses 3.2" — mistakes a macro context indicator for a timing tool, and the historical readings that looked clean in hindsight were rarely clean in real time; extremes can persist and extend well past where they "should" have turned.
The more grounded use is as one input into where a longer cycle currently sits. A high MVRV or Z-score reading is a reason to size positions more conservatively and to be less surprised by a sharp drawdown, not a countdown clock to a top. A reading near or below 1 is a reason to pay attention to accumulation-style behavior and not assume the downtrend is structurally endless, not a green light to go all-in at that exact candle. On a site that scores assets across multiple signals rather than any single indicator, MVRV works best folded in as one macro-context input alongside the others — it tells you roughly where the network's aggregate cost basis sits relative to price, and leaves the timing of any individual decision to everything else you know about the setup.