Block
#18323466
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
868 days ago (Oct-10-2023 11:55:23 PM +UTC)
Transactions:
89 transactions and 45 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.015139204230451845 ETH (0 + 0.122413373170441421 - 0.107274168939989576)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
442,770 bytes
Gas Used:
17,554,516 (58.52%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006110915786 ETH (6.110915786 Gwei)
Burnt Fees:
š„ 0.107274168939989576 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,567.68 / ETH
Hash:
0x518e04198d6e250c29d60399c7ad3fde7904ec3de4b36d24e4cc7629ac2be3ae
StateRoot:
0x1b034034f690b9a80f3988f9d0ec1d301f556e0ccc40a7b4151aa03f9bc43429
WithdrawalsRoot:
0xc8647a8581e324c6345cba8c8363002641cc0d69c2d7913791341960e7c10e08
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1438617c40a2c010df056bc587e10d62f1e590348adf227fba309507853c2909
Parent Root Hash:
0xc621ccba7085e5115e1769a32487c425aa4c49ab4a7287c7990985b6520df40c
Beacon Chain Deposit Count:
997777
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x45ccaa567b2aacb1e9ab9cf990cbff0be1eba3c0693668ada7502270cab5d0c8
Randao Reveal:
0x8077b7cce965b2a97e602495b84bc57a474f39e2cb58e5edf0fb650385d8f9adb6ebc3329f774305a8b264b301d92781168d37e7e6f29eb7b36f4fdb63cb2062c43d6992e6a16ee5a0595222d2577e9dbde474a2aa4ac363bceef859c781bcc6
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.015804085771507599 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.