Contracts
Last updated
Last updated
The sum count of unique contracts that exist in the ledger and that hold a balance (i.e., own a non-zero amount) of native units at the end of the interval. A contract is a special address that contains and can execute code.
| Name | MetricID | Unit | Interval |
|---|---|---|---|
Contracts with no balance in native units are not counted.
This metric is only available for ETH and ETC.
Version 4.2 of CM Network Data Pro Daily Macro (End of Day)
The sum count of unique contracts that exist in the ledger at the end of the interval. A contract is a special address that contains and can execute code.
Contracts with no balance in native units are counted.
This metric is only available for ETH and ETC.
Version 4.2 of CM Network Data Pro Daily Macro (End of Day)
The sum count of unique ERC-20 contracts that exist on the ledger at the end of the interval. A contract is a special address that contains and can execute code. Contracts that contain all of the following are considered to be ERC-20 contracts: the balanceOf function, the transfer function, and the Transfer event hash.
Contracts with no balance in native units are counted.
Full compliance with the ERC-20 standard is not required as only few ERC-20 tokens attain it. We therefore look for the bare minimum methods and events necessary for wallet integration of the token: balanceOf and transfer functions as well as the Transfer event. If a contract’s code has all of the following markers, it is considered to be ERC-20:
Signature of the balanceOf function: 6370a082311461
Signature of the transfer function: 63a9059cbb1461
Hash of the transfer event ddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef
This metric is only available for ETH and ETC.
Version 4.3 of CM Network Data Pro Daily Macro (End of Day)
The sum count of unique contracts that exist in the ledger at the end of the interval. A contract is a special address that contains and can execute code.
Contracts with no balance in native units are counted.
This metric is only available for ETH and ETC.
Version 4.2 of CM Network Data Pro Daily Macro (End of Day)
The sum count of unique contracts implementing the ERC-721 standard that exist in the ledger at the end of the interval. A contract is a special address that contains and can execute code. ERC-165 is used to determine a contract’s compliance with ERC-721.
Contracts with no balance in native units are counted.
ERC-721 contracts are detected if they implement the ERC-165-compatible interface defined in the ERC-721 specification using the procedure specified in the ERC-165 specification.
This metric is only available for ETH and ETC.
Version 4.3 of CM Network Data Pro Daily Macro (End of Day)
The sum count of unique smart contracts implementing the ERC-1155 standard present in the blockchain at the end of the interval. A smart contract exists in a blockchain network as a special address that contains and can execute code. The ERC-1155 standard is an emerging standard for the issuance of both fungible and non-fungible tokens on Ethereum. As of this metric's release date, the standard has attained considerable traction in the ecosystem of Non-Fungible Tokens.
This metric is calculated by monitoring the blockchain for contracts that comply with the ERC-1155 standard_,_ as defined by the EIP-1155 Standard Specification.
Like ERC-721 contracts, the activity of ERC-1155s is detected with the help of a secondary standard, ERC-165, which provides an interface for both 751 as well as 1155-compliant events.
As this metric is tailored to the Ethereum ecosystem, it is only available for ETH .
Released in Network Data Pro (NDP) version 5.1
Contracts metrics can be accessed using these endpoints:
timeseries/asset-metrics
and by passing in the metric ID's Cont* in the metrics parameter.
| Name | MetricID | Unit | Interval |
|---|---|---|---|
| Name | MetricID | Unit | Interval |
|---|---|---|---|
| Name | MetricID | Unit | Interval |
|---|---|---|---|
| Name | MetricID | Unit | Interval |
|---|---|---|---|
| Name | MetricID | Unit | Interval |
|---|---|---|---|
Contracts Cnt with Bal >0
ContBalCnt
Contracts
1 day
Contracts Cnt
ContCnt
Contracts
1 day
ERC-20 Contracts Cnt
ContERC20Cnt
Contracts
1 day
Contracts Cnt
ContCnt
Contracts
1 day
ERC-721 Contracts Cnt
ContERC721Cnt
Contracts
1 day
ERC-1155 Contracts Cnt
ContERC1155Cnt
Contracts
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.