Contracts

Contents

• Contracts Executed Count

• Contracts Executed Successfully Count

• Transactions Invoking Contract Count

• New Created Contracts Count

• Destroyed Contracts Count

Contracts Executed Count

Definition

The sum count of contract calls executed across all transactions in that interval. A contract call is the invocation of a contract’s code by another contract or non-contract address. Failed invocations are counted. A single transaction can result in multiple contract calls.

Name	MetricID	Unit	Interval
Contracts Executed Count	TxContCallCnt	Calls	1 day

Details

• Failed transactions are included.

• Contract creations and destructions are not included.

Asset-Specific Details

• This metric is only available for SOL, ETH and ETC.

Release History

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

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Contracts Executed Successfully Count

Definition

The sum count of contract calls successfully executed across all transactions in that interval. A contract call is the invocation of a contract’s code by another contract or non-contract address. Only successful executions are taken into account.

Name	MetricID	Unit	Interval
Contracts Executed Successfully Cnt	TxContCallSuccCnt	Calls	1 day

Details

• Contract creations and destructions are not included.

Asset-Specific Details

• For Solana, count of all instruction calls from successful transactions, excluding vote instructions

Release History

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

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Transactions Invoking Contract Count

Definition

The sum count of transactions that invoked a contract in that interval. Failed transactions are counted but internal transactions are not (i.e., only the parent transaction is counted). A contract is a special address that contains and can execute code.

Name	MetricID	Unit	Interval
Transaction Invoking Contract Count	TxContCnt	Transactions	1 day

Details

• Failed transactions are counted.

• Contract creations are counted.

• Internal transactions are not counted (i.e., only the parent transaction is counted).

Asset-Specific Details

• This metric is only available for ETH and ETC.

Release History

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

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

New Created Contracts Count

Definition

The sum count of new contracts successfully created across all transactions in that interval. A contract is a special address that contains and can execute code.

Dictionary

Name	MetricID	Unit	Interval
New Created Contracts Count	TxContCreatCnt	Contracts	1 day

Details

• If a transaction creates multiple contracts, each creation is counted once.

Asset-Specific Details

• This metric is only available for ETH and ETC.

Release History

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

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Destroyed Contracts Count

Defintion

The sum count of contracts successfully destroyed across all transactions in that interval. A contract is a special address that contains and can execute code.

Name	MetricID	Unit	Interval
Destroyed Contracts Count	TxContDestCnt	Contracts	1 day

Details

• If a transaction destroys several contracts, each destruction is counted once.

• Not all contract protocols allow contract destruction.

Asset-Specific Details

• This metric is only available for ETH and ETC.

Release History

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

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 TxContCallCnt , TxContDestCnt etc. in the metrics parameter.

Asset metrics

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:

GEThttps://api.coinmetrics.io/v4/timeseries/asset-metrics

Authorization

api_key

Query parameters

Response

200400401403414

Time series of metrics for an asset.

Body

application/jsontext/csv

data*any

next_page_tokenNextPageToken (string)

Token of the next page results for a given request.

next_page_urlNextPageUrl (string)

URL of the next page results for a given request.

Response

200400401403

{
  "next_page_token": "text",
  "next_page_url": "text"
}

Shell

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

Python

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