Block
#18315835
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
870 days ago (Oct-09-2023 10:17:59 PM +UTC)
Transactions:
132 transactions and 80 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.10994789025694878 ETH (0 + 0.244570060988255475 - 0.134622170731306695)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
289,014 bytes
Gas Used:
15,719,755 (52.40%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000008563884789 ETH (8.563884789 Gwei)
Burnt Fees:
š„ 0.134622170731306695 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,580.25 / ETH
Hash:
0x1db427cba6772be70dbbacfea9faa7aaaf82fdd82c7c906d5f39c3142efd781a
StateRoot:
0x49bb5b888cf8549e1cd37151525e346a213aac0e7ac04b9b1db0543eb389fe29
WithdrawalsRoot:
0xe33166948c7d1e95cd180c71768a93bb0a2615cc0d426d55c88bd8ae58e088ee
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc99ae95a2ffa1865c62f6ad5b8348fc2287cbf88ddae471128a435cb9efc19d5
Parent Root Hash:
0xa74d90f730f07369b4d08d81a3859c77975b237f400d4e452111a31a5ecb3ab1
Beacon Chain Deposit Count:
993272
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x3da8bd717983655bbfed8aee8b5ae732468d5103002f908bbc8d4c0235cb593a
Randao Reveal:
0x86679b346b2365655d224fd14e41b49ba2c0ceb0dd8e8becde0dc062d2f1bc717472230bcab7b219634205834bb1822615a02b76a0dae95a25eacc22087b82274b5bdbdea55f91d70ed93d0f73b65cb513795898cf1d4daf9dbbbcd5492650d4
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.110817039870182539 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.