Blocks
Last updated
Last updated
The sum count of blocks created that interval that were included in the main (base) chain.
Name | MetricID | Unit | Interval |
---|---|---|---|
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).
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.
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.
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.
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).
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 (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.
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 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).
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).
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.
Name | MetriID | Unit | Interval |
---|---|---|---|
Name | MetricID | Unit | Interval |
---|---|---|---|
Name | MetricID | Unit | Interval |
---|---|---|---|
Name | MetricID | Unit | Interval |
---|---|---|---|
Name | MetricID | Unit | Interval |
---|---|---|---|
Name | MetricID | Unit | Interval |
---|---|---|---|
Name | MetricID | Unit | Interval |
---|---|---|---|
Name | MetricID | Unit | Interval |
---|---|---|---|
Name | MetricID | Unit | Interval |
---|---|---|---|
Name | MetricID | Unit | Interval |
---|---|---|---|