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 among MEV transactions
- MEV Transfers Above/Below X Amount (Count)
- Sum Value of Payments among MEV 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
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 | USD | 1 day |
Details
TxTfrValContCallNtvis the sum of native units transferred by successful contract calls that interval.TxTfrValContCallUSDis the USD equivalent, computed asTxTfrValContCallNtv × PriceUSD.
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
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
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 / TxTfrCnt
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
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
- TxTfrValMeanUSD 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
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
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
TxTfrValNtv 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 | Transfers | 1 day |
| Xfers Below $1,000, Count | TxTfrValBelUSD1000Cnt | Transfers | 1 day |
| Xfers Below $500, Count | TxTfrValBelUSD500Cnt | Transfers | 1 day |
| Xfers Below $100, Count | TxTfrValBelUSD100Cnt | Transfers | 1 day |
| Xfers Below $50, Count | TxTfrValBelUSD50Cnt | Transfers | 1 day |
| Xfers Below $20, Count | TxTfrValBelUSD20Cnt | Transfers | 1 day |
| Xfers Below $10, Count | TxTfrValBelUSD10Cnt | Transfers | 1 day |
| Xfers Below $5, Count | TxTfrValBelUSD5Cnt | Transfers | 1 day |
Details
- For these metrics, the bands are inclusive of one another. This means that, for example, all transactions included in the TxTfrValBelUSD5Cnt are also included in the TxTfrValBelUSD10Cnt. To get the value for a specific band exclusive of the lower/higher bands, these need to be excluded.
- If you want to only get transfers between $20-$50 you would need to calculate this as TxTfrValBelUSD50Cnt - TxTfrValBelUSD20Cnt
- 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.
- If a network is predominantly being used for retail payments use cases, one would expect transfers under $20 or $10 to occur more frequently than payments above $1000
- 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
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 |
|---|---|---|---|
| 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 $50 (native units) | TxTfrValBelUSD50Ntv | Native Units | 1 day |
| Sum Value of Payments Below $20 (native units) | TxTfrValBelUSD20Ntv | Native Units | 1 day |
| Sum Value of Payments Below $10 (native units) | TxTfrValBelUSD10Ntv | Native Units | 1 day |
| Sum Value of Payments Below $5 (native units) | TxTfrValBelUSD5Ntv | 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 |
| Sum Value of Payments Below $50 (USD) | TxTfrValBelUSD50USD | USD | 1 day |
| Sum Value of Payments Below $20 (USD) | TxTfrValBelUSD20USD | USD | 1 day |
| Sum Value of Payments Below $10 (USD) | TxTfrValBelUSD10USD | USD | 1 day |
| Sum Value of Payments Below $5 (USD) | TxTfrValBelUSD5USD | USD | 1 day |
Details
- For these metrics, the bands are inclusive of one another. This means that, for example, all transactions included in the TxTfrValBelUSD5USD are also included in the TxTfrValBelUSD10USD. To get the value for a specific band exclusive of the lower/higher bands, these need to be excluded.
- If you want to only get transfers between $20-$50 you would need to calculate this as TxTfrValBelUSD50USD - TxTfrValBelUSD20USD
- 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
Xfer'd Val among MEV TXs
| Name | MetricID | Unit | Interval |
|---|---|---|---|
| Xfer'd Val among MEV txs (native units) | MevTfrValNtv | Native Units | 1 day |
| Xfer'd Val among MEV txs (USD) | MevTfrValUSD | USD | 1 day |
Definition
The sum of native units or USD value transferred (i.e., the aggregate size of all transfers) among MEV-enabled transactions between distinct addresses that interval. An MEV-enabled transaction is one that paid an MEV tip to miners/validators in exchange for specific block ordering.
Asset-Specific Details
- For Solana, slots proposed by validators running the Jito-Solana client are considered as MEV slots. Further, in Solana it is possible to identify which transactions paid MEV tip in addition to simply identifying the slot. For this metric each individual transaction is evaluated to determine which are MEV-enabled and which aren't.
Availability for Assets
MevTfrValNtv
MevTfrValUSD
MEV Transfers Above/Below X Amount (Count)
| Name | MetricID | Unit | Interval |
|---|---|---|---|
| Payments Among MEV Txs Above $100k Cnt | MevTfrValAbUSD100kCnt | Transfers | 1 day |
| Payments Among MEV Txs Above $1M Cnt | MevTfrValAbUSD1MCnt | Transfers | 1 day |
| Payments Among MEV Txs Above $10M Cnt | MevTfrValAbUSD10MCnt | Transfers | 1 day |
| Payments Among MEV Txs Above $100M Cnt | MevTfrValAbUSD100MCnt | Transfers | 1 day |
| Payments Among MEV Txs Below $100 Cnt | MevTfrValBelUSD100Cnt | Transfers | 1 day |
| Payments Among MEV Txs Below $500 Cnt | MevTfrValBelUSD500Cnt | Transfers | 1 day |
| Payments Among MEV Txs Below $1000 Cnt | MevTfrValBelUSD1kCnt | Transfers | 1 day |
| Payments Among MEV Txs Below $10000 Cnt | MevTfrValBelUSD10kCnt | Transfers | 1 day |
Definition
The sum count of all unique transfers in MEV-enabled transactions in that interval with a value above or below the specified value in USD terms.
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 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.
Asset-Specific Details
- For Solana, slots proposed by validators running the Jito-Solana client are considered as MEV slots. Further, in Solana it is possible to identify which transactions paid MEV tip in addition to simply identifying the slot. For this metric each individual transaction is evaluated to determine which are MEV-enabled and which aren't.
Availability for Assets
MevTfrValAbUSD1MCnt - representative for coverage of all metrics in this section
Sum Value of Payments among MEV Txs Above/Below X Amount
| Name | MetricID | Unit | Interval |
|---|---|---|---|
| Sum Value of Payments Among MEV Txs Above $100M (native units) | MevTfrValAbUSD100MNtv | Native Units | 1 day |
| Sum Value of Payments Among MEV Txs Above $10M (native units) | MevTfrValAbUSD10MNtv | Native Units | 1 day |
| Sum Value of Payments Among MEV Txs Above $1M (native units) | MevTfrValAbUSD1MNtv | Native Units | 1 day |
| Sum Value of Payments Among MEV Txs Above $100k (native units) | MevTfrValAbUSD100kNtv | Native Units | 1 day |
| Sum Value of Payments Among MEV Txs Above $100M (USD) | MevTfrValAbUSD100MUSD | USD | 1 day |
| Sum Value of Payments Among MEV Txs Above $10M (USD) | MevTfrValAbUSD10MUSD | USD | 1 day |
| Sum Value of Payments Among MEV Txs Above $1M (USD) | MevTfrValAbUSD1MUSD | USD | 1 day |
| Sum Value of Payments Among MEV Txs Above $100k (USD) | MevTfrValAbUSD100kUSD | USD | 1 day |
| Sum Value of Payments Among MEV Txs Below $10000 (native units) | MevTfrValBelUSD10kNtv | Native Units | 1 day |
| Sum Value of Payments Among MEV Txs Below $1000 (native units) | MevTfrValBelUSD1kNtv | Native Units | 1 day |
| Sum Value of Payments Among MEV Txs Below $500 (native units) | MevTfrValBelUSD500Ntv | Native Units | 1 day |
| Sum Value of Payments Among MEV Txs Below $100 (native units) | MevTfrValBelUSD100Ntv | Native Units | 1 day |
| Sum Value of Payments Among MEV Txs Below $10000 (USD) | MevTfrValBelUSD10kUSD | USD | 1 day |
| Sum Value of Payments Among MEV Txs Below $1000 (USD) | MevTfrValBelUSD1kUSD | USD | 1 day |
| Sum Value of Payments Among MEV Txs Below $500 (USD) | MevTfrValBelUSD500USD | USD | 1 day |
| Sum Value of Payments Among MEV Txs Below $100 (USD) | MevTfrValBelUSD100USD | USD | 1 day |
Definition
The sum of all native units or USD transferred that interval by transfers in MEV-enabled transactions with a value above or below the specified USD threshold.
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 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.
Asset-Specific Details
- For Solana, slots proposed by validators running the Jito-Solana client are considered as MEV slots. Further, in Solana it is possible to identify which transactions paid MEV tip in addition to simply identifying the slot. For this metric each individual transaction is evaluated to determine which are MEV-enabled and which aren't.
Availability for Assets
MevTfrValAbUSD100kNtv, representative coverage for all metrics in this section
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.
GET /timeseries/asset-metrics
Asset metrics
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()
)