Block
#17946349
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
918 days ago (Aug-19-2023 04:09:47 AM +UTC)
Transactions:
106 transactions and 40 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.022812139963039022 ETH (0 + 0.193686238915688378 - 0.170874098952649356)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
129,903 bytes
Gas Used:
11,945,516 (39.82%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000014304455241 ETH (14.304455241 Gwei)
Burnt Fees:
š„ 0.170874098952649356 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,669.67 / ETH
Hash:
0xfaed934092e4bf683394a3cc6b316980e88b8656a189be6928cbcb158cfcf94c
StateRoot:
0x9dbf22e9800ae93c2e56bfc7c4df0036f819751db1185714945955e56a2d678a
WithdrawalsRoot:
0xdd955acab3409c672283d01b7f042f0ccd6e3c6ca16b0c3d8190fbf6614887ea
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x61f599546d52384d8afdb46e15a0a5113326a4297c2ba50254d26d4ce51d4bd8
Parent Root Hash:
0x232aad2b4fd6dbdf06660fc1833c6ce6cfbdeda7e17bbce01afd639376116ddd
Beacon Chain Deposit Count:
916330
Slot Graffiti:
Lido ā”ļøAllnodes (Hex:0x4c69646f20e29aa1efb88f416c6c6e6f64657300000000000000000000000000)
Block Randomness:
0xe88b477484c752dd3ff53f4a5466a0f8dc3b50c1979418aab1a00f22f3e15147
Randao Reveal:
0xab4ed0ec9ccc490d4c41c2d4f90e2fdc94caa2b4cc1bde4857498d6441eb86f57e3c3740f5840f488a9f4a75d196a0fc0b0e6a8e07e0f1848bba5d15292e53582b54c56969b7620df92f3540a1335770cc509ba7c27c618083915d44359be3c8
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.022705854153205271 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.