bitunix

Spent Outputs Aged 5y–7y

Range
  • 1M1M
  • 3M3M
  • 6M6M
  • 1Y1Y
  • ALLALL
Scale
  • LinearLinear
  • LogLog
Latest
9.37K
2026-10-27 · 9,367
1D change
-30.66%
Prev. 13.51K
7D change
-15.37%
Prev. 11.07K
30D change
+664.70%
Prev. 1.23K
4Y percentile
96%
All history 99%
All-time high
86.83K
2022-10-14 · -89.21%
1Y range
334 – 46.96K
Since 2009-01-12
Loading data…

About this metric

What it measures

Spent Outputs Aged 5y–7y counts the daily outputs consumed after five to seven years in the unspent set. It reports how many old output records become active, not the number of bitcoins or the number of owners returning.

How to read it

A rise highlights renewed movement in outputs that have been inactive for many years; a decline means fewer are spent from this window. The record was 86,833 on October 14, 2022, while the full-history median is only 70, making the distribution strongly affected by rare events and early zeros.

The network could not contain five-year-old outputs before 2014, so full-history percentiles mix an impossible-age period with later activity. Large wallets may also hold thousands of small outputs of similar age; neither a high count nor a long lifespan proves substantial BTC value moved to exchanges.

Frequency
Daily (UTC 00:00)
Asset
BTC
Type
Single value
Data since
2009-01-12
Latest data
2026-10-27
Data points
6,498

FAQ

Why is the five-to-seven-year history zero in the early years?

Bitcoin began in 2009, so outputs could not reach five years of age before 2014. Those initial zeros are a structural age limit rather than evidence of unusually strong holding behavior.

How can many old outputs move without much BTC being transferred?

Outputs have unequal balances. Thousands of small outputs can be consumed together while representing less BTC than a single large output, so value-weighted volume is needed for scale.

Does reactivation mean the coins were previously lost?

No. The spend shows that these particular outputs could be controlled when they moved. Years of inactivity alone do not establish that private keys were lost or later recovered.