Blocks
Last updated
Was this helpful?
Last updated
Was this helpful?
The sum count of blocks created that interval that were included in the main (base) chain.
Block Cnt
BlkCnt
Blocks
1 day, 1 hour
Only mainchain (non-orphaned/uncles) blocks are counted.
For chains that use median time, the day is defined using it, otherwise, it’s defined using the block’s timestamps.
Every blockchain will have a Block Count measurement as it's a fundamental aspect of the the distributed ledger technology.
The drawdowns in the ETH block counts can be explained by the numerous hard forks. Block difficulty would rise making it harder for miners to find the next block resulting in an increase in time between blocks therefore less blocks are created each day.
Released in the 1.0 release of NDP
Block count is typically rather static, but can vary in blockchains which rely on a poisson process for finding new blocks. In proof-of-work chains with long difficulty adjustment windows and significant variance in block times, like Bitcoin, block count can diverge widely from the expected rate. This can happen during competitions for hashpower around the time of forks, or when a significant amount of hashpower is added or subtracted from the blockchain in a short period.
The count of blocks from the genesis (first) block to the last block of that interval on the main chain (in other words, the total number of blocks ever created and included on the chain).
Block Height
BlkHgt
Blocks
1 block, 1 day, 1 hour
Only mainchain (non-orphaned/uncles) blocks are counted.
For chains that use median time, the day is defined using it, otherwise, it’s defined using the block’s timestamps
Every blockchain will have a Block Height measurement as it's a fundamental aspect of the the distributed ledger technology.
Depending on the blockchain, blocks can be produced at different intervals. The longer a blockchain has been in existence and the faster the blocks are produced, the larger the block height will be. ETH blocks are produced every 14 seconds compared to BTC where blocks are created every 10 minutes or so. Therefore, the block height for ETH will be significantly larger than BTC.
Released in the 4.3 release of NDP
New transactions are grouped and added to new blocks on the blockchain. Each block is linked to the previous one and they essentially are stacked together
The mean time (in seconds) between all the blocks created that interval.
Mean Time Block
BlkIntMean
Seconds
1 block, 1 day, 1 hour
Only mainchain (non-orphaned/uncles) blocks are counted.
For chains that use median time, the day is defined using it, otherwise, it’s defined using the block’s timestamps.
The absolute interval is used (if block n+1 has a timestamp lower than block n, we use the absolute value of the difference in timestamps, see examples).
For the block-by-block frequency, it can be interpreted as the amount of time between the publishing of the previous block and the most recent block.
For example, Block 1 is published at a timestamp of 02:00:00 UTC, Block 2 is published at a timestamp of 02:10:00 UTC, so the BlkIntMean would just be 10m for Block 2.
On average, Litecoin produces blocks every 2.5 minutes where Ethereum takes around 14 seconds on average
If for a day, the blocks are:
The value of BlkIntMean would be (120 + 20 + 160 + 60) / 4 = 90 seconds
Released in the 1.0 release of NDP
Blockchains with shorter block time (and hence a larger sample size per day) will typically have less variance in mean block interval.
The sum of the size (in bytes) of all blocks created that interval.
Sum Block Size (in bytes)
BlkSizeByte
Bytes
1 day, 1 block, 1 hour
Only mainchain (non-orphaned/uncles) blocks are counted.
For chains that use median time, the day is defined using it, otherwise, it’s defined using the block’s timestamps.
This metric is not available for all assets, as some node’s RPC APIs do not expose the size of the blocks.
Released in the 1.0 release of NDP
Can be used to measure and compare blockchains' usages and fees
Can help gauge gas/fee for large transactions:
fee per byte = total block fee/block size (byte)
The mean size (in bytes) of all blocks created that interval.
Mean Block Size (in bytes)
BlkSizeMeanByte
Bytes
1 day
Only mainchain (non-orphaned/uncles) blocks are counted.
For chains that use median time, the day is defined using it, otherwise, it’s defined using the block’s timestamps.
This metric is not available for all assets, as some node’s RPC API do not expose the size of the blocks.
Released in the 1.0 release of NDP
Mean block size is somewhat arbitrary; block count multiplied by mean block size gives you the total data throughput on a blockchain per day. Blockchains with shorter interblock times will often have smaller blocks but may throughput more data than their higher-latency peers.
The sum weight of all blocks created that interval. Weight is a dimensionless measure of a block’s “size”. It is only applicable for chains that use SegWit (segregated witness).
Sum Block Weight
BlkWghtTot
Dimensionless
1 day
Only mainchain (non-orphaned/uncles) blocks are counted.
For chains that use median time, the day is defined using it, otherwise, it’s defined using the block’s timestamps.
This metric is only available for assets that support SegWit.
Released in the 4.9 release of NDP
Block weight is useful to determine how used a chain is.
The sum count of uncle blocks mined in that interval.
Uncle Blocks Cnt
BlkUncCnt
Uncles
1 block, 1 day
Uncle Blocks (also known as Ommer Blocks) are an intrinsic feature of Ethereum.
Unlike Bitcoin, Ethereum does not discard blocks in situations where multiple miners find a valid block of the same height.
Instead, Ethereum rewards secondary miners with so-called Uncle Blocks, which effectively represent a share of the work, as well as the reward, of processing transactions.
Uncle blocks are not included in the asset’s main chain but are referenced by main chain blocks. Both the main chain block and uncle block miners get an extra reward for this.
This metric is only relevant to ETH and ETC
Released in the 4.3 release of NDP
Deprecated post the Ethereum Merge
The more uncle blocks there are, the more uncertainty there might be around the finality of those related payments
The percentage of miner revenue exclusively derived from creating and including uncle blocks in that interval. This is equal to the sum of the uncle inclusion reward (for the main chain block miner) and the uncle rewards (for the uncle block miners) divided by the miner revenue.
Miner Revenue from Uncle Blocks (%)
BlkUncRevPct
Dimensionless
1 day
Uncle Blocks (also known as Ommer Blocks) are an intrinsic feature of Ethereum.
Unlike Bitcoin, Ethereum does not discard blocks in situations where multiple miners find a valid block of the same height.
Instead, Ethereum rewards secondary miners with so-called Uncle Blocks, which effectively represent a share of the work, as well as the reward, of processing transactions.
This metric measures the proportion of rewards that resulted from Uncle Blocks.
This metric is only relevant to ETH & ETC
Release Version: NDP-EOD 4.8 (Nov, 2020)
Deprecated post the Ethereum Merge
The sum rewarded to miners for creating and including uncle blocks in that interval. This includes the uncle inclusion reward (for the main chain block miner) and the uncle rewards (for the uncle block miners).
Uncle Reward (native units)
BlkUncRwd
Native Units
1 block, 1 day
Uncle Reward (USD)
BlkUncRwdUSD
Native Units
1 block, 1 day
Uncle Blocks (also known as Ommer Blocks) are an intrinsic feature of Ethereum.
Unlike Bitcoin, Ethereum does not discard blocks in situations where multiple miners find a valid block of the same height.
Instead, Ethereum rewards secondary miners with so-called Uncle Blocks, which effectively represent a share of the work, as well as the reward, of processing transactions.
Uncle blocks are not included in the asset’s main chain but are referenced by main chain blocks. Both the main chain block and uncle block miners get an extra reward for this.
Only available for ETH and ETC
Released in the 4.3 release of NDP
The mean weight of all blocks created that interval. Weight is a dimensionless measure of a block’s “size”. It is only applicable for chains that use SegWit (segregated witness).
Mean Block Weight
BlkWghtMean
Dimensionless
1 day
Only mainchain (non-orphaned/uncles) blocks are counted.
For chains that use median time, the day is defined using it, otherwise, it’s defined using the block’s timestamps.
This metric is only available for assets that support SegWit.
Released in the 4.2 release of NDP
Block weight is useful to determine how used a chain is. If the mean block weight is close to the maximum block weight possible, then the chain is close to 100% utilization.
The sum weight of all blocks created that interval. Weight is a dimensionless measure of a block’s “size”. It is only applicable for chains that use SegWit (segregated witness).
Sum Block Weight
BlkWghtTot
Dimensionless
1 day
Only mainchain (non-orphaned/uncles) blocks are counted.
For chains that use median time, the day is defined using it, otherwise, it’s defined using the block’s timestamps.
This metric is only available for assets that support SegWit.
Released in the 4.9 release of NDP
Block weight is useful to determine how used a chain is.
Block metrics can be accessed using these endpoints:
timeseries/asset-metrics
and by passing in the metric ID's Blk* in the metrics parameter.
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:
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.
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.
["AdrActCnt","BlkHgt"]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.
1dExample: 1bWhich metric values do you want to see. Applicable only for "reviewable" metrics. You can find them in the /catalog/metrics endpoint.
allPossible values: 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 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.
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.
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.
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.
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.
Inclusive or exclusive corresponding start_* parameters.
trueInclusive or exclusive corresponding end_* parameters.
trueSpecifies 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).
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.
UTCExample: America/New_YorkNumber 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.
100Where 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.
endPossible values: 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.
assetPossible values: 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.
Human-readable formatting of JSON responses.
falseFormat of the response.
jsonPossible values: Nulls are represented as zeros in the response.
falseToken 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" errors for the items you currently don't have access to.
falseIgnore "unsupported" errors for not currently supported by Coin Metrics items.
false