Entity-Adjusted Dormancy
- 1M1M
- 3M3M
- 6M6M
- 1Y1Y
- ALLALL
- LinearLinear
- LogLog
About this metric
What it measures
Entity-Adjusted Dormancy divides entity-adjusted Coin Days Destroyed by the corresponding BTC transfer volume between entities. Measured in days, it estimates the amount-weighted age of transferred coins after filtering recognized movements within the same holder.
How to read it
An increase means older coins carry more weight in inter-entity transfers; a decrease means younger coins dominate. The series reached about 1,220 days on July 14, 2025, compared with a full-history median near 32.7 days. A high reading describes the age composition of flow rather than the total BTC transferred.
Entity ownership is inferred, so unrecognized internal transfers can remain and clustering updates can revise history. A small transfer denominator can amplify the ratio, and even an identified movement between entities does not prove an exchange sale.
- Frequency
- Daily (UTC 00:00)
- Asset
- BTC
- Category
- On-chain Indicators
- Type
- Single value
- Unit
- days
- Data points
- 6,498
FAQ
What does entity adjustment remove from Dormancy?
It aims to exclude transfers among addresses attributed to the same holder. Both destroyed age and transfer volume use the adjusted scope, so the result need not always be below the unadjusted series.
How does Dormancy differ from ASOL?
Dormancy weights age by the BTC amount transferred. Average Spent Output Lifespan weights each counted output equally, so many small outputs can affect ASOL without dominating Dormancy.
Does 200 days mean every transferred coin was held that long?
No. It is a volume-weighted mean. A mix of very young coins and a few large old transfers can produce the same average as a more uniform age distribution.
