Block
#17119664
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1030 days ago (Apr-25-2023 12:18:35 AM +UTC)
Transactions:
119 transactions and 98 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.08116323615319944 ETH (0 + 0.659207386610028535 - 0.578044150456829095)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
79,470 bytes
Gas Used:
16,688,191 (55.63%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000034637915545 ETH (34.637915545 Gwei)
Burnt Fees:
🔥 0.578044150456829095 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,866.48 / ETH
Hash:
0xcfd1f874ad144546c3352c0a6d5bb28caadfac97e31549e0e9ec2d06f7f4450d
StateRoot:
0xe79992c6a8fc56ab65f3a0b115e677df6bcbdca8504990eecce002ca7a227dda
WithdrawalsRoot:
0x4a64bfda31ec5d587a3a175721304fab9e575ed08b19a255b0e5170d6bf4c9e1
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x7c7e07fd46bbed1ebefe72ad72adf781ed24eda0c3f00ef41e30e882c0ba4715
Parent Root Hash:
0x5a048858c60d2f327362d52945f4b083c588b09a347c8e1420a36cce4b50ce98
Beacon Chain Deposit Count:
616284
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xaf16bff2f5f452316057576d6cd4e5a20b94f23e420c3083cd68d6020d023746
Randao Reveal:
0xa6dde7e2e21e1c6d48954ff607498d6f2aae527d9dd9264fb40bce782b5eecc7a1546a13a780297c95b540d871a7a8c115db13752947c2004113d6d11174aed8053c374ccf8cb51a2d0d0c9dbfa21bc25a010e31de614d2615fd02262120e8ca
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.080110001573443683 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.