Block
#20034053
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
627 days ago (Jun-06-2024 04:43:23 PM +UTC)
Transactions:
164 transactions and 64 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.068047218372415306 ETH (0 + 0.368113456420672702 - 0.300066238048257396)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
58,445 bytes
Gas Used:
12,256,122 (40.85%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000024482967618 ETH (24.482967618 Gwei)
Burnt Fees:
š„ 0.300066238048257396 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$3,812.05 / ETH
Hash:
0x2847967c983bc2068621789d51a46acb391e690c2b0788a2fce8e700d48e65d0
StateRoot:
0xb4ec5e441b96da31ce983449f2210e068ab0795afb73509b6b40710b6a2bf0c9
WithdrawalsRoot:
0xd8a37deb785e080edd081c71d00c05756e08dd7ab0061ad309103ab4f370037b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd42a4c518ac9f357cf7ade7452e0033ec86c99b511fbb78973159b1352850229
Parent Root Hash:
0xf94cb38d70492c6c9cd3792fa953cfeb3b36a1ec8963bd549d7244389fa6664b
Beacon Chain Deposit Count:
1519076
Slot Graffiti:
Lighthouse/v5.1.3-f7c7f4f (Hex:0x4c69676874686f7573652f76352e312e332d6637633766346600000000000000)
Block Randomness:
0xc468c93f409c566396de06946d482e4bea5d6b4edf8c35cba62f5089d9832d75
Randao Reveal:
0xb0df513be6e0e1abb7dbec8014c27517950f77c7e88610f38b4566d1dd929e5d8d813ef0237c9827d30cabb2fb9313670ba378e5ad0738af57e989adb77ae400cde9d8503e2caee98bfc69b5f7fe0a717e986601e8698763b1f4573b616ca520
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.077851978023739889 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.