Block
#18697291
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
829 days ago (Dec-02-2023 07:41:35 AM +UTC)
Transactions:
311 transactions and 66 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.032234374888996189 ETH (0 + 0.678356051967386697 - 0.646121677078390508)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
226,578 bytes
Gas Used:
19,900,316 (66.33%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000032467910413 ETH (32.467910413 Gwei)
Burnt Fees:
🔥 0.646121677078390508 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$2,165.60 / ETH
Hash:
0xb0333f79e51a57be244d7dd40fdcc1078b1d845f5246417d9144adb899f4b4a5
StateRoot:
0x80b4f54b2ab422cbaaca477492ce9ac1bff5c9fa6f38c8600401092beeeffa6e
WithdrawalsRoot:
0x36f6adc6f5683014dffb24426bf34d233e967ef552f38ac94f7f4c0ffbe50d0f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xcdcc81d8712f9b263e463c173551de81f3a2d9014464aa9b28a3644d3331105f
Parent Root Hash:
0x82b40d94e900ccd7b26bcdf6fb78ef478dda0c82b7a9fb91e7c495806a19a372
Beacon Chain Deposit Count:
1089479
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xd1d1774f00349fee0afe2ec60aa4046fbf0bad91e967181b954dd627adabec55
Randao Reveal:
0xa49331aac0c498698675c77198b03e09d4758617a5fbe0449ae95cddcf1076ebd64d5b752d962a195d727349942e4c7402dfb438284450b20e128033e4b22a2f2f65591c92b668eddbef02735c42c33870e4812bc5a8f8839a7705c07b6b7f87
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.031916476921854346 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.