Block
#17496103
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
984 days ago (Jun-17-2023 12:57:47 AM +UTC)
Transactions:
97 transactions and 41 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.011631146428120486 ETH (0 + 0.193264920422286119 - 0.181633773994165633)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
56,911 bytes
Gas Used:
11,726,491 (39.09%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000015489183763 ETH (15.489183763 Gwei)
Burnt Fees:
š„ 0.181633773994165633 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,727.25 / ETH
Hash:
0x1a8c17f1250e68d4966ae8b2b64e33dd5547422a0e2858cacbb6f3056e66ba30
StateRoot:
0x84e507acad754afde35220597df66d5794dc3870e3c0111a81b5cbe3ed87c3b0
WithdrawalsRoot:
0x4ec53676ec00971811849509a4bb2c238b394dbd1c8d0039ae48c62216a5d58b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x8f0fdec928442e1dc80094865d42d20d4fac50f3eee06f5665a01d70a84ac250
Parent Root Hash:
0xe67d94b1f1355734fd306cf4ca452480caf60457cfc73e01d69e27e3daadbcad
Beacon Chain Deposit Count:
806051
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x08a9b1b7ea12a6ae704f22e2e1e524e01ad60417a3406cc4ed1c4756c7d981e8
Randao Reveal:
0xa3a2a9809af6c8a32041313ed27bf15bdf655e4d43bd284066ea516e04349aa3ea6d8c106c7c9ef403c6cf045354387103495f8a4aa6d77997d1b7524d68e6597840082a0863f0a53bbfa99094c8738d9245c1c8eb8e61bb1af0b9efc42aacec
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.077182362268080815 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.