Block
#18066758
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
928 days ago ()
Transactions:
146 transactions and 62 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x333...203 in 12 secs
Block Reward:
0.113454505832643946 ETH (0 + 0.267886876427497297 - 0.154432370594853351)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
49,496 bytes
Gas Used:
12,279,267 (40.93%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012576676653 ETH (12.576676653 Gwei)
Burnt Fees:
🔥 0.154432370594853351 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,633.84 / ETH
Hash:
0x2979a565b60f2da6a916978f46170cc80ad25a8a4ac87a7f644670dc5446472c
StateRoot:
0x3e012b529eb5deb08c1937d7b385ec40321af0de333f62013d82586cfbc80ab1
WithdrawalsRoot:
0xeb00e457ba2343585cb9212bd6f41760cc9885ac408e329c2daba1e3c0f29aa3
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x8a131101d246988bbac4c2209fa3f42ef840b250f3e4d258d2aa19e482962f7a
Parent Root Hash:
0x90b363931f3b28ec39f4a4ec9846e04cf31a5b638701df047a7b9a2b1b0ecb69
Beacon Chain Deposit Count:
946993
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x00145d72f54263e9ea78fca44bad3bedee0a79b1908d52833be8f03ef11da542
Randao Reveal:
0xb99751c9e9a1b600d2eab1b444996ec3b4a3df1cfdedafbd4d8c577f48f8eb8a4999dfa0dc1d9be0050fbc5cf10bb273162303f20f83b2da200a5e19c20155e25aee248a171131366c2cc4916a14b88bd30e5d9d00fc9b7f801187f2f6d1e8b7
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.113176422935169463 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.