Block
#18379913
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
875 days ago (Oct-18-2023 09:26:47 PM +UTC)
Transactions:
120 transactions and 70 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.067889052032320254 ETH (0 + 0.185442444755027069 - 0.117553392722706815)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
88,181 bytes
Gas Used:
12,139,891 (40.47%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000009683232965 ETH (9.683232965 Gwei)
Burnt Fees:
🔥 0.117553392722706815 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,563.66 / ETH
Hash:
0xbfca7eaae7f51aa3b8079173e2167e6345b5462cfad0aa96fef0d9363f647be9
StateRoot:
0x0420d1cdfaf132cbafbe225dd4706d44bf4bd464b9e3e48d7f828cfec85510dc
WithdrawalsRoot:
0x7ec8e1c548aa7c86802ef0ceab55ed899d3889c939c734deb3107ae1bbdc7e57
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x215c9b759c504501727720c31f1ec15a55366a70397fd703f553a9f3d9220ccc
Parent Root Hash:
0xb515d61852c2c243b2ce6bd8443c6a1792f7e20124ad0c859b120e9fc96a1325
Beacon Chain Deposit Count:
1010980
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x18a8d624211bf68d46976b2f0f737173373478b4db129c7ffd26d4766adb4e9c
Randao Reveal:
0xa8612471c0cf4362c833629171889b3dd96263ab88a01fe4ff82066eaa96adf2c40e9a397f776b84dc1706c4c3aa1b7418427e79b532fa32e8418f1530f3e7304a2f284af963e4f980a53a9295529d6982a8fbc389ba23064fdf182a54be70cf
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.068074946068231139 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.