Block
#18732927
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
812 days ago (Dec-07-2023 07:28:11 AM +UTC)
Transactions:
181 transactions and 68 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.046001781515426914 ETH (0 + 0.690676747469408734 - 0.64467496595398182)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
158,252 bytes
Gas Used:
19,593,772 (65.31%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000032902034685 ETH (32.902034685 Gwei)
Burnt Fees:
🔥 0.64467496595398182 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$2,356.77 / ETH
Hash:
0xfe7a4eb30f5d646bbd4291ab23ecec624951293c2b089514770e1443b223993c
StateRoot:
0x1506c49eabd8d153bc1de8baa5820faec68bfdd7a9d8fd1737790ff814bd093b
WithdrawalsRoot:
0x6eac0c49046eb57f8a605a5db330b74d3f08b701b0df3bf842ee69c7c477c7c8
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x36db622895af1eed220d99c8286b9a8c062e1793f28a9efb28fb6b7446aeb86a
Parent Root Hash:
0x7c69c6620f0ba6671e7bb62743a354ed913e01f977edde9be3e30bc48ad46f93
Beacon Chain Deposit Count:
1102995
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x92cc68d39438f8b80db252c2e45d6bc20ab1f9003334a45963f4432679fbeea5
Randao Reveal:
0x8d7862a6c928f10ee8fb41bdb4a8ee17a3cd8a9198d63454debe7a0db074b6cc0fca99cf9c12438a98421c7578c5587718eb37dc3141ae8ef35b91227edda9f167dd2709de104d79d3c8f2d2d2a6135102df024c1134e1fd5383656a128dbabe
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.060075539585546879 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.