Block
#18528853
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
849 days ago (Nov-08-2023 05:53:23 PM +UTC)
Transactions:
146 transactions and 54 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.047024723603286357 ETH (0 + 0.583508890576659317 - 0.53648416697337296)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
64,731 bytes
Gas Used:
12,823,648 (42.75%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000041835534395 ETH (41.835534395 Gwei)
Burnt Fees:
🔥 0.53648416697337296 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,889.05 / ETH
Hash:
0xd57744ec17f7dfdf176583efb1bcd0ee699f5e588a288d94a95faa84fdefd7ed
StateRoot:
0x504c8cd5446f91465209b46af301a96b8e9edd84ac0674806455a6fc7473a2de
WithdrawalsRoot:
0x4d87267e032178997fb0dee6ba9189a71233d99f8bd924caf6eb769df1d42269
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x835f9864152455a4aabe35883cd083de30fc7f190849d4216cf80ccfb0c49b44
Parent Root Hash:
0xc4756b1d76a371eca3dda2d880c7f9c1c758d7509d1a0e146a94dc644f61f188
Beacon Chain Deposit Count:
1046449
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x4defd07b61dedf1387ce959e1c3e84ee29d17f3351dad1a97752b39af793419e
Randao Reveal:
0xa61515f9ae882ab38f6b44014d5e9de9d6cb61eb3744c1b11e6baa10f8ce259c4a540876a138b0c9f56fc7b5f95c3c8b16a06dbc2dd60a066433e8679358ecb90ce9b9c2647e51ae1a8909c60019da5687cd05d609f7449c5b963cbf1203f72c
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.050631098102278511 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.