Transfer Value

Contents

• Xfer'd Val, Adj

• Xfer'd by Contract Calls

• Xfer'd Days Destroyed

• Mean Xfer'd Days Destroyed

• Mean Tx Size

• Median Tx Size

• Xfer'd Val

• Payments Above/Below X Amount (Count)

• Sum Value of Payments Above/Below X Amount

Xfer'd Val, Adj

Definition

The sum of native units or USD transferred that interval removing noise and certain artifacts. Also known as Adjusted Transfer Value.

Name	MetricID	Unit	Interval
Xfer'd Val, Adj (native units)	TxTfrValAdjNtv	Native units	1 day
Xfer'd Val, Adj (USD)	TxTfrValAdjUSD	USD	1 day

Details

• For UTXO chains, the heuristics used are:

  • Early spend: outputs spent one hour or less after being created are not counted

  • Round numbers: if one output has much more precision than the other outputs in the same transaction, it’s not counted. For example, if a transaction creates 2 outputs, one of 1.00000000 BTC and one of 0.2561278 BTC, the second one would not be counted.

  • Self churn: outputs that have the same address as any of the inputs addresses are discounted

  • Also removed are cold wallet shuffles (when an exchange changes their cold wallet addresses) and other artifacts such as noise generated by early Bitcoin applications like Satoshi Dice

• For account chains, this metric is computed as the sum number of native units received by accounts, whose net balance did change in that hour.

Asset-Specific Details

• For assets that have opt-in privacy features, like ZCash, it only takes the non-private activity.

Example

• If in the same hour:

  • ** Account A sends 50 units to B

  • ** Account C sends 50 units to A

  • ** Account B sends 50 units to E

  • ** Account D sends 49 units to B

• Then:

  • ** Account A has a net balance change of 0, received 50

  • ** Account B has a net balance change of -1, received 99

  • ** Account C has a net balance change of -50, received 0

  • ** Account D has a net balance change of -49, received 0

  • ** Account E has a net balance change of +50, received 50

• *** Unadjusted volume is 199

• *** Adjusted volume is 149 (B: 99, E: 50)

Release History

• Released in the 1.0 release of NDP

Availability for Assets

• TxTfrValAdjNtv
• TxTfrValAdjUSD

Xfer'd by Contract Calls

Definition

The sum of all native units or USD transferred by contract calls on that interval. A contract call is the invocation of a contract’s code by another contract or non-contract address. Only successful calls are considered.

Name	MetricID	Unit	Interval
Xfer'd by Contract Calls (native units)	TxTfrValContCallNtv	Native units	1 day
Xfer'd by Contract Calls (USD)	TxTfrValContCallUSD	Native units	1 day

Details

• TxTrfValContCallNtv is computed as TxTfrValAdjNtv / BlkSizeByte

• TxTrfValContCallUSD is computed as TxTfrValAdjUSD / BlkSizeByte

• This metric estimates the economical density of an asset.

Asset Specific Details

• For SOL this metric measures the value transferred by instructions which sent value to program-derived accounts. Excludes vote accounts and externally-owned accounts.

Release History

• Released in the 4.2 release of NDP

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Coin Metrics CoverageCoin Metrics Coverage

Xfer'd Days Destroyed

Definitions

The sum of all native units transferred that interval multiplied by the sum of days since those native units were last transferred.

Name	MetricID	Unit	Interval
Xfer'd Days Destroyed	TxTfrValDayDst	Dimensionless	1 day, 1 block

Details

• Days destroyed is a measure of time * money.

• When an unspent output is spent, the time it stayed unspent (in days) is multiplied by its value, this metric measures the sum of these coin days spent in a given day.

• Only full days are taken into account (2.5 days count as 2 days)

Asset-Specific Details

• Only available for UTXO chains.

• For assets that have opt-in privacy features, like ZCash, it only takes the non-private activity.

Release History

• Released in the 1.0 release of NDP

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Mean Xfer'd Days Destroyed

Definition

The mean per transaction of the sum of all native units transferred multiplied by the sum of days since those native units were last transferred that interval.

Name	MetricID	Unit	Interval
Mean Xfer'd Days Destroyed	TxTfrValDayDstMean	Dimensionless	1 day

Details

• Computed as TxTfrValDayDst / TxCnt

Asset-Specific Details

• Only available for UTXO chains

• For assets that have opt-in privacy features, like ZCash, it only takes the non-private activity.

Release History

• Released in the 1.0 release of NDP

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Mean Tx Size

Definition

The sum value of native units or USD transferred divided by the count of transfers (i.e., the mean size of a transfer) between distinct addresses that interval.

Name	MetricID	Unit	Interval
Mean Tx Size (native units)	TxTfrValMeanNtv	Native units	1 day, 1 hour
Mean Tx Size (USD)	TxTfrValMeanUSD	USD	1 day, 1 hour

Details

• TxTfrValMeanNtv is computed as TxTfrValNtv / TxTfrCnt

• TxTfrValMeanNtv is computed as TxTfrValMeanNtv * PriceUSD

Asset-Specific Details

• For assets that have opt-in privacy features, like ZCash, it only takes the non-private activity.

Release History

• Released in the 1.0 release of NDP

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Median Tx Size

Definition

The median count of native units or USD transferred per transfer (i.e., the median "size" of a transfer) that interval.

Dictionary

Name	MetricID	Unit	Interval
Median Tx Size (native units)	TxTfrValMedNtv	Native units	1 day, 1 hour
Median Tx Size (USD)	TxTfrValMedUSD	USD	1 day, 1 hour

Details

• Transfers are movement of native units.

• Only non-zero value, successful, transfers with distinct sender/recipient, are considered.

Asset-Specific Details

• For assets that have opt-in privacy features, like ZCash, it only takes the non-private activity.

Release History

• Released in the 1.0 release of NDP

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Xfer'd Val

Definition

The sum of native units or USD transferred (i.e., the aggregate "size" of all transfers) that interval. Also known as Transfer Value (native units).

Name	MetricID	Unit	Interval
Xfer'd Val (native units)	TxTfrValNtv	Native units	1 day, 1 hour
Xfer'd Val (USD)	TxTfrValUSD	USD	1 day, 1 hour

Details

• Transfers are movement of native units.

• Only non-zero value, successful, transfers with distinct sender/recipient, are considered.

• Failed transactions are not considered in TxTfrValNtv

• For ETH, the fees sent from the original sender to the miner for the failed transaction are not considered

• This metric counts transfers between two addresses, exluding transfers from or to the null account (issuance account) as those would be considered mints (transfers from) and burns (transfers to). These would be counted in our SplyCur metric as an increase or decrease in the supply.

Asset-Specific Details

• For assets that have opt-in privacy features, like ZCash, it only takes the non-private activity.

Release History

• Released in the 1.0 release of NDP

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

TxTfrValNtv Coverage

Coin Metrics CoverageCoin Metrics Coverage

TxTfrValUSD Coverage

Payments Above/Below X Amount (Count)

The sum count of payments (transfers) above or below X worth of a cryptoasset at the time the transfer took place.

Name	MetricID	Unit	Interval
Payments Above $100M Cnt	TxTfrValAbUSD100MCnt	Transfers	1 day
Payments Above $10M Cnt	TxTfrValAbUSD10MCnt	Transfers	1 day
Payments Above $1M Cnt	TxTfrValAbUSD1MCnt	Transfers	1 day
Payments Above $100k Cnt	TxTfrValAbUSD100kCnt	Transfers	1 day
Xfers Below $10,000, Count	TxTfrValBelUSD10000Cnt	Addresses	1 day
Xfers Below $1,000, Count	TxTfrValBelUSD1000Cnt	Addresses	1 day
Xfers Below $500, Count	TxTfrValBelUSD500Cnt	Addresses	1 day
Xfers Below $100, Count	TxTfrValBelUSD100Cnt	Addresses	1 day

Details

• This metrics shows the incidence (count) of payments above/below each of the supported thresholds.

• Payments are defined as transfers (xfers) and represent the individual asset transfers within a transaction.

• A transaction may be a collection of transfers which, specially in UTXO-based blockchains, may represent several P2P payments.

• A cryptoasset exchange, for example, may engage in transaction batching whereby user withdraws are aggregated in a single transaction comprised of multiple outputs.

• Each of the outputs represents a transfer. And while each transfer (output) may be going to different users, they are all processed within the same transaction.

• For this reason, this metric is calculated at the transfer-level so all individual payments are accounted for.

• In this version of this metric, change outputs are not adjusted. This means not only peer-to-peer tranfers are accounted for, but also when a user sends fund to their own wallets.

  • For example, if after paying each of the users withdrawing, the exchange still has a remaining balance, the change output is still accounted for in this metric if it falls below the metric's threshold.

  • In other words, if the recipients listed in a transaction's output require payments that, when added together, have a value that is lower than the input, a change output that goes back to the sender must be created. In such circumstances, this metric would also account for the change output if it fell under the measuring threshold.

Interpretation

• This thresholds in this metric can be used to better understand the type of users interacting with a cryptoasset network.

• For example, if a network is predominantly being used for retail transactions, one would expect payments under $100 to occur more frequently than payments above $10,000.

• Similarly, it can show the predominance of different types of investors, such the balance between retail and institutional investors within a network.

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

TxTfrValAb/BelUSDXCnt Coverage

Sum Value of Payments Above/Below X Amount (native units)

The sum of all payments (transfers) that have occurred in the measuring interval above or below X worth of a cryptoasset, displayed in native units (e.g. BTC).

Name	MetricID	Unit	Interval
Sum Value of Payments Above $100M (native units)	TxTfrValAbUSD100MNtv	Ntv	1 day
Sum Value of Payments Above $10M (native units)	TxTfrValAbUSD10MNtv	Ntv	1 day
Sum Value of Payments Above $1M (native units)	TxTfrValAbUSD1MNtv	Ntv	1 day
Sum Value of Payments Above $100k (native units)	TxTfrValAbUSD100kNtv	Ntv	1 day
Sum Value of Payments Above $100M (USD)	TxTfrValAbUSD100MUSD	USD	1 day
Sum Value of Payments Above $10M (USD)	TxTfrValAbUSD10MUSD	USD	1 day
Sum Value of Payments Above $1M (USD)	TxTfrValAbUSD1MUSD	USD	1 day
Sum Value of Payments Above $100k (USD)	TxTfrValAbUSD100kUSD	USD	1 day
Sum Value of Payments Below $10k (native units)	TxTfrValBelUSD10000Ntv	Native Units	1 day
Sum Value of Payments Below $1k (native units)	TxTfrValBelUSD1000Ntv	Native Units	1 day
Sum Value of Payments Below $500 (native units)	TxTfrValBelUSD500Ntv	Native Units	1 day
Sum Value of Payments Below $100 (native units)	TxTfrValBelUSD100Ntv	Native Units	1 day
Sum Value of Payments Below $10k (USD)	TxTfrValBelUSD10000USD	USD	1 day
Sum Value of Payments Below $1k (USD)	TxTfrValBelUSD1000USD	USD	1 day
Sum Value of Payments Below $500 (USD)	TxTfrValBelUSD500USD	USD	1 day
Sum Value of Payments Below $100 (USD)	TxTfrValBelUSD100USD	USD	1 day

Details

• This metrics shows the sum of payments above/below each of the supported thresholds.

• Payments are defined as transfers (xfers) and represent the individual asset transfers within a transaction.

• A transaction may be a collection of transfers which, specially in UTXO-based blockchains, may represent several P2P payments.

• A cryptoasset exchange, for example, may engage in transaction batching whereby user withdraws are aggregated in a single transaction comprised of multiple outputs.

• Each of the outputs represents a transfer. And while each transfer (output) may be going to different users, they are all processed within the same transaction.

• For this reason, this metric is calculated at the transfer-level so all individual payments are accounted for.

• In this version of this metric, change outputs are not adjusted. This means not only peer-to-peer tranfers are accounted for, but also when a user sends fund to their own wallets.

  • For example, if after paying each of the users withdrawing, the exchange still has a remaining balance, the change output is still accounted for in this metric if it falls below the metric's threshold.

  • In other words, if the recipients listed in a transaction's output require payments that, when added together, have a value that is lower than the input, a change output that goes back to the sender must be created. In such circumstances, this metric would also account for the change output if it fell under the measuring threshold.

Interpretation

• The thresholds supported by this metric family can be used to better understand the type of users interacting with a cryptoasset network.

• For example, if a network is predominantly being used by whales, one would expect payments above $1M USD to occur more frequently than payments below $10 USD.

• Similarly, it can show the predominance of different types of investors, such the balance between retail and institutional investors within a network.

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

API Endpoints

Token Transaction metrics can be accessed using these endpoints:

• timeseries/asset-metrics

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

Asset metrics

get

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:

Authorizations

Query parameters

assetsstring[]Required

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.

metricsstring[]Required

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.

Example: ["AdrActCnt","BlkHgt"]

frequencystringOptional

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.

Default: 1dExample: 1b

statusstring · enumOptional

Which metric values do you want to see. Applicable only for "reviewable" metrics. You can find them in the /catalog/metrics endpoint.

Default: allAvailable options:

start_timestringOptional

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_timestringOptional

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.

start_heightinteger · int64Optional

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.

end_heightinteger · int64Optional

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.

start_hashstringOptional

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.

end_hashstringOptional

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.

start_inclusivebooleanOptional

Inclusive or exclusive corresponding start_* parameters.

Default: true

end_inclusivebooleanOptional

Inclusive or exclusive corresponding end_* parameters.

Default: true

min_confirmationsinteger · int32 · max: 99Optional

Specifies 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).

timezonestringOptional

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.

Default: UTCExample: America/New_York

page_sizeinteger · int32 · min: 1 · max: 10000Optional

Number 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.

Default: 100

paging_fromstring · enumOptional

Where 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.

Default: endAvailable options:

sortstring · enumOptional

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.

Default: assetAvailable options:

limit_per_assetinteger · int32Optional

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.

prettybooleanOptional

Human-readable formatting of JSON responses.

Default: false

formatstring · enumOptional

Format of the response.

Default: jsonAvailable options:

null_as_zerobooleanOptional

Nulls are represented as zeros in the response.

Default: false

next_page_tokenstringOptional

Token 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_errorsbooleanOptional

Ignore "forbidden" errors for the items you currently don't have access to.

Default: false

ignore_unsupported_errorsbooleanOptional

Ignore "unsupported" errors for not currently supported by Coin Metrics items.

Default: false

Responses

application/jsontext/csv

objectOptional

Time series of asset metrics.

application/json

application/json

application/json

get

HTTPcURLJavaScriptPython

GET /v4/timeseries/asset-metrics HTTP/1.1
Host: api.coinmetrics.io
Accept: */*

{
  "data": [
    {
      "asset": "btc",
      "time": "2020-02-29T00:00:00.000000000Z",
      "PriceUSD": "8582.09029964933",
      "SplyBMXNtv": "283220.10827406",
      "SplyBMXNtv-status": "reviewed",
      "SplyBMXNtv-status-time": "2020-03-01T09:59:13.847251000Z"
    },
    {
      "asset": "btc",
      "time": "2020-03-01T00:00:00.000000000Z",
      "PriceUSD": "8541.77389392169",
      "SplyBMXNtv": "284691.32323907",
      "SplyBMXNtv-status": "reviewed",
      "SplyBMXNtv-status-time": "2020-03-02T14:00:02.622168000Z"
    }
  ],
  "next_page_token": "0.MjAyMC0wNi0wN1QwMDowMDowMFo,MjAyMC0wNi0wN1QwMDowMDowMFo",
  "next_page_url": "https://api.coinmetrics.io/v4/timeseries/asset-metrics?api_key=<your_key>&pretty=true&assets=btc&metrics=SplyBMXNtv,PriceUSD&page_size=2&next_page_token=0.MjAyMC0wNi0wN1QwMDowMDowMFo,MjAyMC0wNi0wN1QwMDowMDowMFo"
}

Shell

curl --compressed "https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=TxTfrValAdjNtv&assets=eth&pretty=true&api_key=<your_key>"

Python

import requests
response = requests.get('https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=TxTfrValAdjNtv&assets=eth&pretty=true&api_key=<your_key>').json()
print(response)

Python Client

from coinmetrics.api_client import CoinMetricsClient

api_key = "<API_KEY>"
client = CoinMetricsClient(api_key)

print(
    client.get_asset_metrics(
        metrics="TxTfrValAdjNtv", 
        assets="eth",
    ).to_dataframe()
)