Active Supply
Last updated
Was this helpful?
Last updated
Was this helpful?
The sum of unique native units that transacted at least once in the trailing X time to that interval. Native units that transacted more than once are only counted once.
1 Day Active Supply
SplyAct1d
Native units
1 days
7 Day Active Supply
SplyAct7d
Native units
7 days
30 Day Active Supply
SplyAct30d
Native units
30 days
90 Day Active Supply
SplyAct90d
Native units
90 days
180 Day Active Supply
SplyAct180d
Native units
180 days
1 Year Active Supply
SplyAct1Yr
Native units
1 Year
2 Year Active Supply
SplyAct2Yr
Native units
2 Years
3 Year Active Supply
SplyAct3Yr
Native units
3 Years
4 Year Active Supply
SplyAct4Yr
Native units
4 Years
5 Year Active Supply
SplyAct5Yr
Native units
5 Years
Active Supply (transacted at least once)
SplyActEver
Native units
All time
For UTXO-based protocols, active supply is considered as the outputs created during the time interval. Mining reward outputs are not considered active. If an address has an output created outside the time interval, and inside the time interval, only the latter output will be considered active.
For account-based protocols, active supply is the sum of the balances of accounts that were either created outside of token generation events (genesis, mining, etc.) during the considered time interval, or that had at least one native units debit during it. Any type of movement suffice to mark an account as active (fees, transfers, etc.).
For Ripple, escrows are considered active supply, with a last active time at the time of their creation.
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.
Released in the version 4.0 of Network Data Pro
This metric tracks the fraction of supply active in the trailing period specified. This allows you to determine how active given tranches of a cryptocurrency are. This is a distinct and harder to forge metric than transactional value (see for instance Transactions, transfers, value, adjusted, USD), which can be increased by a few whales making copious self-sends. In active supply, one’s ability to game the metric is proportional to one’s share of supply. The worst an adversary could do would be to make their fraction of supply appear perpetually active. Active supply cohorts are a popular tool used by traders to access the market-relevant supply of an asset and to ascertain whether a given asset is being used transactionally or as a store of value. Additionally, the longer-term active supply cohorts can be used to derive an estimate of lost coins.
The percentage of the current supply that has been active in the trailing 1 year up to that day.
1 Year Active Supply %
SplyActPct1yr
Dimensionless
1 day
Computed as SplyAct1yr / SplyCur
For UTXO chains, active supply is considered as the outputs created during the considered time interval. Mining reward outputs are not considered active. (If an address has an output created outside the time interval, and inside the time interval, only the latter output will be considered active).
For account based chains, active supply is the sum of the balances of accounts that were either created outside of token generation events (genesis, mining, etc.) during the considered time interval, or that had at least one outgoing native units movement during that time period.
For Ripple, escrows are considered active supply, with a last active time at the time of their creation.
This metric is not available for assets that have full privacy, like Monero, Grin.
For assets that have opt-in privacy features, like ZCash, it only takes the non-private balances into account.
Released in the 1.0 release of NDP
1-year active supply % is the percent of total supply that has been transferred on-chain within the last year. As an asset price rises, an increasing amount of dormant supply can start to become active as long-term holders sell or move their native units. Some view a high percentage of 1-year active supply in the trailing year as a sign that a price rally is reaching exhaustion. Conversely, when price is low for extended periods of time, 1-year active supply % has dropped historically as investors hold through crypto winters.
Active Supply metrics can be accessed using these endpoints:
timeseries/asset-metrics
and by passing in the metric ID's SplyAct* in the metrics parameter.
Returns requested metrics for specified assets. Results for block by block metrics (1b frequency) are ordered by tuple (asset, height, block_hash), all other metrics are ordered by tuple (asset, time). You can change the sorting using sort query parameter. Supported output formats are json (default) and csv, use format query parameter to override it. To fetch the next page of results use next_page_url JSON response field or x-next-page-url CSV HTTP header if present. If multiple metrics are requested in the same time the strict policy for partially available metrics among requested ones is applied:
Comma separated list of assets. Use the /catalog-all/assets endpoint for the full list of supported assets or specify asterisk (*) in order to get metrics for all supported assets.
Comma separated metrics to request time series data for. Information on all available metrics can be found on page https://coverage.coinmetrics.io/asset-metrics-v2. Use the /catalog-all/metrics or /catalog-all/assets endpoint for the full list of supported metrics per asset.
["AdrActCnt","BlkHgt"]Frequency of the metrics. Supported values are 1b (block by block), 1s (one second), 1m (one minute), 5m (five minutes), 10m (ten minutes), 1h (one hour), 1d (one day), 1d-ny-close (one day at New York close time). Please refer to the /catalog/metrics endpoint for the full list. Use the /catalog-all/assets endpoint for the full list of supported frequencies per asset-metric pair.
1dExample: 1bWhich metric values do you want to see. Applicable only for "reviewable" metrics. You can find them in the /catalog/metrics endpoint.
allAvailable options: Start of the time interval. This field refers to the time field in the response. Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z, 2006-01-20T00:00:00.000Z, 2006-01-20T00:00:00.123456Z, 2006-01-20T00:00:00.123456789Z, 2006-01-20, 20060120. Inclusive by default. Mutually exclusive with start_height and start_hash. UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it. If start_time is omitted, response will include time series from the earliest time available.
End of the time interval. This field refers to the time field in the response. Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z, 2006-01-20T00:00:00.000Z, 2006-01-20T00:00:00.123456Z, 2006-01-20T00:00:00.123456789Z, 2006-01-20, 20060120. Inclusive by default. Mutually exclusive with end_height and end_hash. UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it. If end_time is omitted, response will include time series up to the latest time available.
The start height indicates the beginning block height for the set of data that are returned. Inclusive by default. Mutually exclusive with start_time and start_hash.
The end height indicates the ending block height for the set of data that are returned. Inclusive by default. Mutually exclusive with end_time and end_hash. This parameter is disabled for Community users.
The start hash indicates the beginning block height for the set of data that are returned. Inclusive by default. Mutually exclusive with start_time and start_height.
The end hash indicates the ending block height for the set of data that are returned. Inclusive by default. Mutually exclusive with end_time and end_height.
Inclusive or exclusive corresponding start_* parameters.
trueInclusive or exclusive corresponding end_* parameters.
trueSpecifies how many blocks behind the chain tip block by block metrics (1b frequency) are based on. Default for btc is 2 and 99 for eth. For example, a min_confirmations of 0 means metrics are being calculated for the block at the tip of the chain (the latest block received by our node) whereas a min_confirmations of 6 means that metrics are being applied to the block that is 6 blocks behind the chain tip (i.e., the 7th block if the chain tip is block 1).
Timezone name for start_time and end_time timestamps. This parameter does not modify the output times, which are always UTC. Format is defined by TZ database.
UTCExample: America/New_YorkNumber of items per single page of results. The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.
100Where does the first page start, at the start of the interval or at the end. The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.
endAvailable options: How results will be sorted. Metrics with 1b frequency are sorted by (asset, height, block_hash) tuples by default. Metrics with other frequencies are sorted by (asset, time) by default. If you want to sort 1d metrics by (time, asset) you should choose time as value for the sort parameter. Sorting by time is useful if you request metrics for a set of assets.
assetAvailable options: How many entries per asset result should contain. For example, this combination of parameters assets=btc,eth&metrics=ReferenceRate&limit_per_asset=1 returns the latest ReferenceRate values for btc and eth.
Human-readable formatting of JSON responses.
falseFormat of the response.
jsonAvailable options: Nulls are represented as zeros in the response.
falseToken for receiving the results from the next page of a query. Should not be used directly. To iterate through pages just use next_page_url response field.
Ignore "forbidden" errors for the items you currently don't have access to.
falseIgnore "unsupported" errors for not currently supported by Coin Metrics items.
falseTime series of asset metrics.