Supply-Adjusted CDD (Supply-Adjusted Coin Days Destroyed) weighs spent coin time against how many coins there are to spend, which puts a figure from one decade on the same footing as a figure from another. This is the one to reach for when the question spans cycles.

Raw coin-day destruction grows on its own. There are more coins in existence than there were, and they have existed for longer, so the raw figure drifts upward whether or not anybody’s behaviour has changed. Adjusting removes that drift and leaves the behavioural part.

What it actually measures

The metric asks what share of the network’s accumulated coin time is being spent, rather than how many coin days were destroyed in absolute terms. An early-era reading and a recent one then describe the same quantity, which the unadjusted series cannot claim.

That is what qualifies it for the long view. A reading that stays elevated for weeks says a genuinely larger slice of the network’s stored time is on the move, and that is what distribution feels like while it is happening rather than how it looks on one memorable afternoon.

Normalising changes which days were the biggest

The adjustment does not simply flatten the series, it re-ranks it. Early-era events grow relative to their neighbours because they occurred against a much smaller supply, and modern events shrink for the same reason. Days that look unremarkable on the raw chart can be among the largest here, and the reverse is also true.

So the answer to which was the biggest destruction day in Bitcoin’s history depends entirely on which version you are reading, and both answers are correct in their own terms. Raw CDD answers how much moved. This series answers how much moved relative to what existed. Neither is the true one.

What it does not tell you

It inherits every ambiguity of the raw series. Custody consolidation, exchange reshuffles and self-transfers destroy coin days without a change of owner, and normalising by supply does nothing to separate them from genuine distribution.

It is also less useful for the recent past than the raw series. Measured against an ever-growing supply, modern readings are damped, so an event that genuinely matters for today’s market can look modest beside something from a decade ago. Comparability across eras is bought at the cost of sensitivity within one.

How to read it

Elevated. A large share of the network’s accumulated coin time is being spent. High against full history, the footprint of distribution.

Mid-range. The share being spent sits in its ordinary range, describing background conditions.

Subdued. Barely any of the stored time is on the move, so the seasoned supply is dormant. That has generally been the accumulation end of the range.

Supply-Adjusted CDD is drawn on the Dormancy dashboard, beside Coin Days Destroyed, Coin Years Destroyed and Binary CDD.

Common questions

Why adjust for supply at all?

Because the unadjusted number swells for no better reason than that more coins have existed for longer. Take that drift out and what is left is the behaviour.

When should this be used instead of raw CDD?

Any time the question spans more than one cycle. The unadjusted series swells as the network does, behaviour or no behaviour, so a figure from the early years and one from last month are not measuring the same thing.

What is a long stretch at the top saying?

A regime rather than an incident. With size removed from the equation, a reading that stays elevated for weeks means a genuinely larger slice of the stored time is being spent.

Does it remove whale distortion?

No. One very large, very old output still dominates a single day. For that problem, Binary CDD is the better instrument because it counts days rather than size.

Which version should be the default?

Raw CDD for recent events, this one for historical comparison. Reading the pair together is more informative than choosing between them.