Entity-Adjusted Coin Days Destroyed
- 1M1M
- 3M3M
- 6M6M
- 1Y1Y
- ALLALL
- LinearLinear
- LogLog
About this metric
What it measures
Entity-Adjusted Coin Days Destroyed measures daily BTC transferred between identified entities multiplied by the age attributed to those coins, in BTC-days. Same-entity transfers are filtered so recognized internal reshuffles do not count as new economic spending or reset age in the same way as raw output accounting.
How to read it
A large reading means substantial accumulated age has moved between entities, through older coins, a larger BTC amount, or both. The series reached about 259.9 million BTC-days on July 29, 2019, versus a full-history median near 6.9 million, illustrating its sensitivity to concentrated old-coin activity.
Entity labels are inferred and may change, and movement between different entities still need not be a market sale. Adjusted values are not guaranteed to sit below raw CDD because preserving age through internal transfers can later increase age counted on an external transfer.
- Frequency
- Daily (UTC 00:00)
- Asset
- BTC
- Category
- On-chain Indicators
- Type
- Single value
- Unit
- BTC-days
- Data since
- 2009-01-03
- Latest data
- 2026-10-27
- Data points
- 6,507
FAQ
Can Entity-Adjusted CDD exceed ordinary CDD?
Yes. Internal transfers reset age in raw output accounting but can preserve it in entity-based accounting. When those coins later leave the entity, the adjusted age can be greater, so filtering internal moves does not imply a lower reading every day.
Does a spike prove long-term holders sold BTC?
It establishes that a large amount of age moved under the entity model. Custody changes and other transfers between distinct participants can also create high readings without an exchange sale.
How does CDD differ from ASOL?
CDD sums BTC amount multiplied by age and is measured in BTC-days. ASOL averages the lifespan of eligible spent outputs in days, giving output count rather than BTC amount the weighting role.
