Block
#18322628
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
874 days ago (Oct-10-2023 09:06:59 PM +UTC)
Transactions:
115 transactions and 54 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.017886882464645144 ETH (0 + 0.111350542763066799 - 0.093463660298421655)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
105,322 bytes
Gas Used:
11,076,505 (36.92%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000008438010031 ETH (8.438010031 Gwei)
Burnt Fees:
🔥 0.093463660298421655 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,567.68 / ETH
Hash:
0x93475eec7e26618e440947c32c5efa2f87ffc04637306c06b945d0f6f9e68218
StateRoot:
0xbc84ae3e5585d6d51a6e1b69a75aa3489fc398f1394623d5cdc9b72fb3009079
WithdrawalsRoot:
0x79095f5e522c964cc78445fc1b235985f4a87d28dcf728b76cbc6ecae63dd3fc
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x85080d8994326c6fbb18253247e4114424c92684a60c5e8c48b876dc86182f1c
Parent Root Hash:
0x07c28eb279e34c4b4430558dbd05e53c1e801451d36ad9d7feef825b239ac4f2
Beacon Chain Deposit Count:
997777
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x0b09b0db6362bd9a0818742dd73ca349fb8d07f14c60f41c909a3eda11fcf2d7
Randao Reveal:
0x92b3d6b69d72569d2667b1d8e4c5f12df091c038d7a4ef700170a3eea4e2514ca05ba10dbbe3470b7c1d51e44f3c93b60168865ad23e455c773dc89ee061340306ffd19afca846e8b7b63cb3beb3e803e6b5f830427f0ede22690825b3f211ba
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.018923684365724703 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.