Blocks

The base fees paid to the network (i.e. burnt) per gas unit.

This metric is in wei.

The minimum MEV rewards calculated in the block, outside of any priorityFees. Read more about the calculation methodology here.

These are the public keys of the builder that built a particular block.

The timestamp of when the block was recorded on based on the genesis of the chain.

The hash indicating the specific consensus slot.

Indicates whether a proposer proposed a Consensus Layer slot (proposed) or missed a proposal (missed).

These are the proposal rewards from the Ethereum Consensus Layer (Beacon Chain).

The slot number in the Ethereum Consensus Layer (Beacon Chain).

The epoch number of a particular slot. Each epoch has 32 slots.

The hash indicating the specific execution block.

The block number in the Ethereum Execution Layer

Indicates whether a proposer proposed a block that contains transactions (proposed), a block with no transactions (empty), or completely missed a proposal (missed).

The rewards from the Ethereum Execution Layer.

This is the sum of totalPriorityFeesValidator and baselineMev.

The address that received the block rewards on the Ethereum Execution Layer.

The Consensus Layer rewards missed by a validator for not being able to propose a slot. Read more about how this is estimated here.

The Execution Layer rewards missed by a validator for not being able to propose a block or by proposing an empty block. Read more about how this is estimated here.

The mev-boost relays where a particular block was sourced from.

The gas fees burnt for the set of transactions in the particular block.

This metric is in wei.

The gas units used by the set of transactions in the particular block.

The transaction fees paid by the end-user to the block’s feeRecipient.

The portion of the totalPriorityFees that were paid to the validator that proposed the block. Given that the feeRecipient of a block can be the builder (as opposed to the proposer itself), it is up to the builder how much they pay to the validator in terms of the priority fees the former captured from building the block.

The sum of consensusRewards and executionRewards.

The sum of missedConsensusRewards and missedExecutionRewards.

The count of transactions that involve one or more addresses (i.e. in to and from addresses) that are in any sanctions lists by government bodies.

The total count of transactions in the particular block.

The count of type0 transactions.

Type0 Ethereum transactions are legacy transactions; this was the main transaction type before the EIP-1559 upgrade. Despite being referred to as “legacy”, these are still in use after the upgrade.

The transaction fees generated by type0Transactions.

This metric is in wei.

The count of type1 transactions.

Type1 transactions are transactions that contain an access list, which is a list of addresses and storage keys that the transactions plan to access.

The transaction fees generated by type1Transactions.

This metric is in wei.

The count of type2 transactions.

Type2 Ethereum transactions were introduced with the EIP-1559 upgrade.

The transaction fees generated by type2Transactions less any burntFees.

The index of the validator assigned to propose for that particular slot/block.