Block
#18486661
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
824 days ago (Nov-02-2023 08:05:47 PM +UTC)
Transactions:
228 transactions and 85 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.089433851837434105 ETH (0 + 0.685035041983092913 - 0.595601190145658808)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
203,938 bytes
Gas Used:
20,427,336 (68.09%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000029157066303 ETH (29.157066303 Gwei)
Burnt Fees:
🔥 0.595601190145658808 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,801.34 / ETH
Hash:
0x08ca50c626a64cb9068f2e201b134b0ac7b384ab5eaa0db7e2073929781e7525
StateRoot:
0x04194bea0f02489f298962301707f1f7c479b2a96a3bd486164f742f3832ddab
WithdrawalsRoot:
0x33adc201b70a0bbb85f95efcd04bdc59b1f480a2f83a4c5f81dae07441ef9d34
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x55aecda2ae2b4583c688b99a1dd088bacddaa5998a3ef9d1b018f66dba4040f3
Parent Root Hash:
0x1f462cebc4591cce2011adfb8b6432bdf0d657e82317f4a76b0d1e7d46b5d2dc
Beacon Chain Deposit Count:
1032970
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xff58da6970cf4622233577f8da8800cb02607720f0ed2f4811e9e843b9debd90
Randao Reveal:
0xaf1c0a8b736d2b426a0e451e967f6689612ba84d416a6545398a608ea7b92d095f7a39868adde8d4913764a814cab9b900ce6a804ec82ea42b22ef82e3d087811615e6f5949dc77075783073172bafa98a4ac9923e697df058199cbdb1220084
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.089189159944408472 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.