Block
#18675836
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
798 days ago (Nov-29-2023 07:40:11 AM +UTC)
Transactions:
164 transactions and 79 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.056877533692314001 ETH (0 + 0.530333075036667001 - 0.473455541344353)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
255,546 bytes
Gas Used:
15,201,390 (50.67%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.0000000311455427 ETH (31.1455427 Gwei)
Burnt Fees:
🔥 0.473455541344353 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,029.17 / ETH
Hash:
0x9693edaba574a14be5ff02d772cdd523d1fe4d5752d2e5fc07fc67d132676b57
StateRoot:
0x3d6540c6017416a6cb235b810a93a94ed28983ffa21649ecba75736c0d75b031
WithdrawalsRoot:
0x6fe1cecb45a0281648a1aa7aaa89bf8108d843ad900b24dc85c32c9809e82aea
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x8bc113f679e067392b2cfbbc563bf07d29251987804abd4de399e6fe15af1e65
Parent Root Hash:
0x5879c7fb11c0545dc3fc015c24db911ae4c919143c0f0f7e82004099cf47ebab
Beacon Chain Deposit Count:
1082204
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x461e33a46bdd53cac932416c917c73608e7600b196625691491ac7dcb8007dd3
Randao Reveal:
0xa5304a8a6a65f18470b207b93ef7b1aa24f280fbe9f972eeb6053006076b3ac4fe7b47192b9a4d5bc4ef18ae4a1acf5c02757149d52eeeaa5de30d603210f3eb651d5fd8514d2466ac13145eef36dcfbebe3c508c805e6a53d129a13060a3038
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.05983278073700343 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.