Block
#18115825
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
899 days ago (Sep-11-2023 09:34:35 PM +UTC)
Transactions:
135 transactions and 73 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.102975131802107559 ETH (0 + 0.423029312270706748 - 0.320054180468599189)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
56,805 bytes
Gas Used:
19,346,143 (64.55%)
Gas Limit:
29,970,705
Base Fee Per Gas:
0.000000016543565323 ETH (16.543565323 Gwei)
Burnt Fees:
🔥 0.320054180468599189 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,551.73 / ETH
Hash:
0x2f486301840e537cfa5487de44ff81fa3875361d47d69a83cf9d4bcfd9148e38
StateRoot:
0xdcffe9d193697a7b27af462b23e6c24369a590fedc53d126f60ac624d590ef93
WithdrawalsRoot:
0x55ab13da4b5c71de25af3e2b7d529c2a5604f9c7601cefc491793e717abdca2b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x872e7dd1379fb289df33085d48231cf61d11187cfa09281a09860dc3fe52c971
Parent Root Hash:
0x41f169a2f7036953e0816eed0988a599629f4043502d05f2c43fa72bfe994be1
Beacon Chain Deposit Count:
954081
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x0733bc1a869a45cfa0235cfc5355110ed3ad2019e82ec8ddf10718000bdefb16
Randao Reveal:
0x94c246601d7e50c0c83db913980d4f9b84da1dde503eb2e1b8749416736f3d677dbafc52adc732f9e2d760d126b6c0ab028f78da66208538527079b2e1e6da627cbaf645b2c1430196fd7c1c3c8dc0e1266f435d1ca99ae74d7d9676c27cac38
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.102819337029250706 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.