Block
#18534869
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
831 days ago (Nov-09-2023 02:05:11 PM +UTC)
Transactions:
241 transactions and 68 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.057545144726981901 ETH (0 + 0.977365708791757061 - 0.91982056406477516)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
367,401 bytes
Gas Used:
18,442,780 (61.48%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000049874290322 ETH (49.874290322 Gwei)
Burnt Fees:
🔥 0.91982056406477516 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,121.13 / ETH
Hash:
0x92f7eff6c0e53a0b7b6a4e61d9111cf8fc0e4c8f0787de679c9ac629343f8729
StateRoot:
0xc18c2f572b09293fa139437aea130552fd9fc832840799316a1351a38f891cf8
WithdrawalsRoot:
0x329f9e52baf8472a4925cb89b1d0de584c0c1c1ffb31dce513d0d86c3a19b9c6
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x65b353259c80e1e90905654267b87ca5ae57aee1f49354ff5b37d9d270c5569a
Parent Root Hash:
0x77bcc296d2abf57ae2a452ac0cecf3e116c51cbf7469da598eda30832acb798b
Beacon Chain Deposit Count:
1049821
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x6e6c15d1bcfff5192943212006d84eac38b3c63c08f7c327cb3338b7747b423d
Randao Reveal:
0xb6a4f11e9c8f0d9145249219e9183ea309f16c15d1206b59a472c128ab9710b0249aaf97bf5b7e237ef57608994fbc790f896c37826efe006a95ca50d22d2a4ef6ea59241dcd5f27b6b840ec26cc3433b74816472eb2aa56d46c0da81c77b8d8
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.066802555940673621 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.