Block
#17225556
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1026 days ago (May-09-2023 09:29:11 PM +UTC)
Transactions:
193 transactions and 138 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.743827796190557164 ETH (0 + 2.232870793955687224 - 1.48904299776513006)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
69,992 bytes
Gas Used:
15,811,578 (52.71%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000009417421827 ETH (94.17421827 Gwei)
Burnt Fees:
🔥 1.48904299776513006 ETH
Extra Data:
by @builder0x69 (Hex:0x627920406275696c64657230783639)
Ether Price:
$1,849.03 / ETH
Hash:
0x1ee4b456fd3a2fcaeb703ee5ab65e6ff389ec757a66b32d5b6dc410bde529619
StateRoot:
0x79f6922eb20066cc60431a68e2def47561dcce4e2c79337a0f3c08d223a81ed3
WithdrawalsRoot:
0x2bfe66c775ed625d57212a2d7ef9f43609703fd7cbb2ed86cc1b7765ee3887f0
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd91a71d59e884e3912ccfbdebce44c8bb454e9741444d8118dd32ab029962784
Parent Root Hash:
0xadf1a14a3801e04f02393de67600de382762eedfe5936898dc88055cad7e66dc
Beacon Chain Deposit Count:
666643
Slot Graffiti:
prylabs-lido (Hex:0x7072796c6162732d6c69646f0000000000000000000000000000000000000000)
Block Randomness:
0x600306dd4db64317c01eaaef7a997414e8bde4911cd6c4da98192e30843ec899
Randao Reveal:
0xa2309e858a34eafd4679bc67ea12394cc97de00044abdf8303c1da8a5c23d4449983ec3aa825c7815c05cc86f59d22481263d8d3fd6cf493586540bae7e8041b3442f72719ac210147977904d230a4da20a14ec8f50f2784b457436b8c52a9a3
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.794254888724496726 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.