Block
#17216803
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1029 days ago (May-08-2023 03:56:35 PM +UTC)
Transactions:
156 transactions and 54 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.111683381717171969 ETH (0 + 1.731000716669975313 - 1.619317334952803344)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
58,846 bytes
Gas Used:
11,485,988 (38.29%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000140981980388 ETH (140.981980388 Gwei)
Burnt Fees:
🔥 1.619317334952803344 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,853.92 / ETH
Hash:
0x8a182b4ab29aa253b54bbb043a3770c006b47acec46407011575c322e6c6580a
StateRoot:
0x548bca7908e7cc73e072a437c48e7cdafcfe621adf383897d7307ee6df3a2abb
WithdrawalsRoot:
0xe4b61a8bda96697059927d30c475738eaa959a3e4699e89ffebe8cb81fdd836c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xa39af1ba538a7245f83b4f01bdaf16b8c146db68f01bbfa49ae40c9f2d42db02
Parent Root Hash:
0x20edf47296ba08f77580a9132038b0041b60d33bf0faca837ded458783baaf89
Beacon Chain Deposit Count:
664024
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xd92318c84a8febc8e7053bede7256d073ba7c30932c65c65cebbfbb3a2030488
Randao Reveal:
0x8b30a802394fe05d17c5364a07de29af02733240362b91a560903114521d0f1e85e2e1d828703ca170555a308da6c74016094aa5627e5851066e70e32088e48032fbb7075e1f4d4ae07dca8e19f1416cb727b93146bce6ab874ca7c9b462e2d3
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.165713366485259464 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.