The minimum MEV rewards calculated in the block, outside of any
priorityFees. Read more about the calculation methodology here.Indicates whether a proposer proposed a Consensus Layer slot (
proposed) or missed a proposal (missed).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 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 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 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 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 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 count of type2 transactions.Type2 Ethereum transactions were introduced with the EIP-1559 upgrade.