Active Wallets
Last updated
Last updated
The sum count of unique wallets that were active in the network (either as a destination or source of a ledger change) that day. All unique wallets involved in a ledger change action (recipients and originators) are counted. This metric does not double-count wallets. In other words, if a wallet has been deemed active by being part of a ledger change, it is not counted again if is subsequently involved in a transaction during the same time interval. Wallets represent groups of addresses that we estimate are owned by the same entity. They provide a better proxy for user behavior since users often own more than one blockchain address.
Wallets represent groups of addresses that we estimate are owned by the same entity. In order to group addresses together, we employ a clustering methodology based on well-established industry standards.
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, it only takes the non-private activities into account.
For Solana, this metric captures the count of owner accounts.
Released in version 5.1 of Network Data Pro
The sum count of unique wallets that were active in the network as a recipient of funds. All unique wallets that have received funds in transactions are counted. This metric does not double-count wallets. In other words, if a wallet has been deemed active by receiving funds, it is not counted again if it receives funds again during the same time interval. Wallets represent groups of addresses that we estimate are owned by the same entity. They provide a better proxy for user behavior since users often own more than one blockchain address.
Wallets represent groups of addresses that we estimate are owned by the same entity. In order to group addresses together, we employ a clustering methodology based on well-established industry standards.
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, it only takes the non-private activities into account.
Released in version 5.1 of Network Data Pro
The sum count of unique wallets that were active in the network as a sender of funds. All unique wallets that have sent funds in transactions are counted. This metric does not double-count wallets. In other words, if a wallet has been deemed active by sending funds, it is not counted again if it sends funds again during the same time interval. Wallets represent groups of addresses that we estimate are owned by the same entity. They provide a better proxy for user behavior since users often own more than one blockchain address.
Wallets represent groups of addresses that we estimate are owned by the same entity. In order to group addresses together, we employ a clustering methodology based on well-established industry standards.
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, it only takes the non-private activities into account.
Released in version 5.1 of Network Data Pro
Address Balances can be accessed using these endpoints:
timeseries/asset-metrics
and by passing in the metric IDs WalActCnt
, WalActSentCnt
, etc. in the metrics
parameter.
Name
MetricID
Unit
Interval
Wallets, active, count
WalActCnt
Wallets
1 day
Name
MetricID
Unit
Interval
Wallets, active, received, count
WalActRecCnt
Wallets
1 day
Name
MetricID
Unit
Interval
Wallets, active, sent, count
WalActSentCnt
Wallets
1 day
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:
Time series of metrics for an asset.
Token of the next page results for a given request.
URL of the next page results for a given request.