Block
#17211293
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1023 days ago (May-07-2023 09:22:11 PM +UTC)
Transactions:
144 transactions and 88 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.558788677154104615 ETH (0 + 2.582954197831206571 - 2.024165520677101956)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
60,250 bytes
Gas Used:
15,037,372 (50.12%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000134608994223 ETH (134.608994223 Gwei)
Burnt Fees:
š„ 2.024165520677101956 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,879.53 / ETH
Hash:
0x9ff2be5a998c0a121c2ea968b61293b2fd42dce72777f74f6fdbdf3e5c567b1f
StateRoot:
0xae22a8fa7eb19cf6a1ad74e19d580f81af8a7411f033c6fd732f6bcd06e577b7
WithdrawalsRoot:
0xcfcdd328380ecfd67819cba00c109780b9dd79e10dbfe11efa6f7612a54ebc36
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x41c0b9b4d8b8814c959873d0bf8eaa2fac923575cb66646bbb3ce6f5c6071e3d
Parent Root Hash:
0x47cff6d3b3ef199daa373ab5e9c58ebfe33685d58e9897de3f17973625d7db8f
Beacon Chain Deposit Count:
660244
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x6c4903ac02149b056bea92178b221f0baa5237a0d9a7fce6dac867d35a533d3b
Randao Reveal:
0xaa8ac7e2a794ad4d93d8c4ce9d6f39e27600f37f9c056c0ace845557e79663e6a57bbe1de2fe9f52c43e03af21156f9a06fec2ac475b73b9d79a000662cf47819bd84bc4d8995392da16d1c153c91337b13424247ca66caff66df25e83911ff7
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.524285964534899819 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
Blocks are batches of transactions linked via cryptographic hashes. Any tampering of a block would invalidate all following blocks as all subsequent hashes would change. Learn more about this page in our Knowledge Base.