Transactions

Contents

• Tx Cnt

• Tx per Second Cnt

• Tx Mean Size

• OP_RETURN Tx Cnt

• Shielded Tx Cnt

• Fully Shielded Tx Cnt

• Transactions, count, vote

• Transactions, count, nonvote

Tx Cnt

Definition

The sum count of transactions that day. Transactions represent a bundle of intended actions to alter the ledger initiated by a user (human or machine). On certain occasions, transactions are counted regardless of whether they result in the transfer of native units or not. As long as such transactions are recorded on the chain, they will be included in the calculation of this metric. Changes to the ledger algorithmically mandated by the protocol, such as coinbase transactions or post-launch new issuance, are not included here.

Name	MetricID	Unit	Interval
Tx Cnt	TxCnt	Transactions	1 day, 1 hour

Details

• For UTXO chains, this metric doesn’t include coinbase transactions.

Asset Specific Details:

• For Solana, includes all successful and unsuccessful transactions, including vote transactions.

Chart

Source: Coin Metrics Network Data Chart

Release History

• Released in the 1.0 release of NDP

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Tx per Second Cnt

Definition

The sum count of transactions divided by the number of seconds that day.

Name	MetricID	Unit	Interval
Tx per Second Cnt	TxCntSec	Transactions per second	1 day

Details

• Computed as TxCnt / 86400

Asset Specific Details

• For Solana, includes vote transactions

Release History

• Released in the 1.0 release of NDP

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

EIP1559 Tx Cnt

Definition

The sum count of transactions that have natively adopted EIP-1559 features by featuring a Base Fee and Miner Tip.

EIP1559 introduced a host of changes to Ethereum's fee mechanism. While this proposal was implemented as a hard fork, not all wallets have adopted this new transaction type upon activation.

Transactions that are EIP1559-compliant have two portions: a Miner Tip and a Base Fee. Miner Tips represent the portion of the total transaction fees that rewards miners. This serves as an optinal incentive mechanism for miners to prioritize transactions that have opted-in and paid a tip. Base Fees, on the other hand, are mandatory and represent the minimum amount needed to be paid for a transaction to be included in a block. After inclusion, the Base Fee is effectively taken out of circulation, and it is burnt (destroyed).

Name	MetricID	Unit	Interval
EIP1559 Tx Cnt	TxEIP1559Cnt	Transactions	1 day

Details

• EIP1559 was a highly anticipated proposal that changes how transaction fees are priced in Ethereum, as well as the dynamics of block sizes.

• The proposal activated on the Ethereum Network in August of 2021 and marks one of the biggest changes in monetary policy in the history of cryptoassets.

• Instead of the legacy gas price, 1559 splits transaction fees into two distinct fields: a Base Fee and an optional Tip (also known as a Priority Fee).

• This metric calculates the total number of native EIP-1559 transactions that have occurred in the network over the measuring period (e.g. 1 day).

• For a thorough review of EIP1559 and the design of its pricing mechanism, please refer to this paper.

Chart

157KB

Coin_Metrics_Network_Data_2022-09-14T15-07.png

image

Source: CM Network Data Charts

Interpretation

• Not all wallets have implemented EIP-1559 upon activation, so this metric serves as a proxy for the native adoption of this new transaction type.

• While all transactions must abide by EIP-1559 at the blockchain consensus layer (and at the very least carry a Base Fee), not all wallets have natively adopted this transaction fomat.

• This metric serves a proxy to measure the native adoption of EIP1559 by wallets across the network.

• The ratio of TxEIP1559Cnt and Tx Cnt provides a view of the adoption of 1559 natively, relative to all other transactiosn that have taken place in the network.

Release History

• Released in the 5.0 release of NDP (August, 2021)

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Tx Mean Size

Definition

The mean size (in bytes) per transaction for all transactions that interval.

Name	MetricID	Unit	Interval
Tx Mean Size	TxMeanByte	Bytes	1 day, 1 block

Details

• Computed as BlkSizeByte / TxCnt

Release History

• Released in the 1.0 release of NDP

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

OP_RETURN Tx Cnt

Definition

The sum count of transactions in that interval that included at least one OP_RETURN output. OP_RETURN outputs are used to embed data into the blockchain database.

Name	MetricID	Unit	Interval
OP_RETURN Tx Cnt	TxOpRetCnt	Transactions	1 day

Details

• Coinbase (i.e., miner reward) transactions are not included.

• This metric is only available for Bitcoin and its forks/derivatives.

Release History

• Version 4.2 of CM Network Data Pro Daily Macro (End of Day)

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Shielded Tx Cnt

Definition

The sum count of transactions using opt-in privacy features that interval. All privacy related features are included (including fully shielding, shielding, deshielding or mixed transactions). Transactions represent a bundle of intended actions to alter the ledger initiated by a user (human or machine). Shielding a transaction hides some or all of the activity described by it to a blockchain observer.

Name	MetricID	Unit	Interval
Shielded Tx Cnt	TxShldCnt	Transactions	1 day

Details

• Transactions in assets with opt-in privacy features can be of several types:

  • Fully shielding: all senders and all recipients are unknown

  • Shielding: all senders are known, all recipients are unknown

  • Deshielding: all senders are unknown, all recipients are known

  • Mixed: some senders are unknown or/and some recipients are unknown

  • Transparent: all senders and recipients are known

• This metric includes all transaction types except transparent

Asset-Specific Details

• This metric is only available for assets that have opt-in privacy features like ZCash and its derivatives

Release History

• Version 4.5 of CM Network Data Pro Daily Macro (End of Day)

• Date Last Modified: 2019-01-10

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Fully Shielded Tx Cnt

Definition

The sum count of transactions using fully shielding privacy features that interval. Only fully shielding transactions are included (transactions with partial or mixed shielding are not included). Transactions represent a bundle of intended actions to alter the ledger initiated by a user (human or machine). Fully shielding a transaction hides all of the activity of a transaction (except for the miner fee it paid).

Name	MetricID	Unit	Interval
Fully Shielded Tx Cnt	TxShldFullCnt	Transactions	1 day

Details

• Transactions in assets with opt-in privacy features can be of several types:

  • Fully shielding: all senders and all recipients are unknown

  • Shielding: all senders are known, all recipients are unknown

  • Deshielding: all senders are unknown, all recipients are known

  • Mixed: some senders are unknown or/and some recipients are unknown

  • Transparent: all senders and recipients are known

• This metric includes all transaction types except transparent

Asset-Specific Details

• This metric is only available for assets that have opt-in privacy features like ZCash and its derivatives

Release History

• Version 4.5 of CM Network Data Pro Daily Macro (End of Day)

• Date Last Modified: 2019-01-10

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Transactions, count, vote

Definition

The sum count of non-voting transactions that interval on Solana. A subset of TxCnt.

Name	MetricID	Unit	Interval
Transactions, count, vote	TxCntVote	Transactions	1 day

Details

• For Solana, count of all transactions on the Solana network that are vote transactions. Does not include other transactions.

Release History

• Added as part of the first release of Solana metrics

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Transactions, count, nonvote

Definition

The sum count of non-voting transactions that interval on Solana. A subset of TxCnt.

Name	MetricID	Unit	Interval
Transactions, count, nonvote	TxCntNonvote	Transactions	1 day

Details

• For Solana, count of all transactions on the Solana network that are not vote transactions.

Release History

• Added as part of the first release of Solana metrics

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 TxCnt, TxCntSec etc. 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: allPossible values:

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: endPossible values:

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: assetPossible values:

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: jsonPossible values:

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

Shell

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

Python

import requests
response = requests.get('https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=TxCnt&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="TxCnt", 
        assets="eth",
    ).to_dataframe()
)