Revived Supply


Supply Revived in Last X Days/Years


The sum of all native units balances last active X days/years that became active in this interval.


Supply Revived in Last 7 Days


Native units

7 days

Supply Revived in Last 30 Days


Native units

30 days

Supply Revived in Last 90 Days


Native units

90 days

Supply Revived in Last 180 Days


Native units

180 days

Supply Revived in Last 1 Year


Native units

1 Year

Supply Revived in Last 2 Years


Native units

2 Years

Supply Revived in Last 3 Years


Native units

3 Years

Supply Revived in Last 4 Years


Native units

4 Years

Supply Revived in Last 5 Years


Native units

5 Years


  • For UTXO chains, revived supply is considered as the outputs created before the considered time interval and spent at the time of the metric's computation. For example, if an address has one output created inside the time interval, and one output created outside of the time interval, only the latter will be considered revived.

  • For account based chains, revived supply is the sum of the balances of accounts that were either created before the considered time interval and that had no activity afterwards, or that had no outgoing native units movement during that period. Any type of movement is sufficient to mark an account as active (fees, transfers, etc.).

Asset-Specific Details

  • This metric is not available for assets that have full privacy, like Monero and Grin.

  • For assets that have opt-in privacy features, like ZCash, we only take the non-private balances into account.


Revived supply gives a more granular look into supply activity. Revived supply is calculated by summing up the amount of supply that has become active after being inactive for at least X days(or years). For example, “Supply Revived in Last 7 Days” is the amount of supply reactivated (on a daily basis) after remaining dormant for at least 7 days.

Availability for Assets

API Endpoints

Revived Supply metrics can be accessed using these endpoints:

  • timeseries/asset-metrics

and by passing in the metric ID's SplyRvv* in the metrics parameter.

curl --compressed "<your_key>"

Last updated