Block
#17935883
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
921 days ago (Aug-17-2023 04:59:35 PM +UTC)
Transactions:
145 transactions and 82 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.037438532061711988 ETH (0 + 0.832099981308151708 - 0.79466144924643972)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
138,968 bytes
Gas Used:
15,138,570 (50.46%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000052492504196 ETH (52.492504196 Gwei)
Burnt Fees:
š„ 0.79466144924643972 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,681.86 / ETH
Hash:
0x429e059aa5e38f13f61102c7759d0b8e715e254823bb48a7e4b6dadb93b9fdb9
StateRoot:
0xbe445c66f5187be2b481e80e5824cff4f8dc6a84bc0d5b72f9c69e727356c00d
WithdrawalsRoot:
0x97067062d35c324aa4227ab8f8d3a6d1638e5bb8ed35c7afff21a45a4d75d574
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xfcf7c0d92f07b2930c58b18a9afc3f392638737f8a477b2cc4a9d1698293fea7
Parent Root Hash:
0xfc9d5699bd445f99a0945822dbfe143f071e50ba188ed3240d0ecc1a2ca4a605
Beacon Chain Deposit Count:
913308
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x0c7d0e1d0327b374cebe5061f4531c9e052fa5f447588c4152099cfd7e37e197
Randao Reveal:
0x907d43bca9cbc14e40421dd36a7ad9b09b445c2032e0ae64e9af71429b50edbb699cde73544e2290cef1be5cfc67313b02fd20e35a0ee816623121a1c70ad1f480ac8ec68735f8d946fdb753a16709de31c06760b435ec85acb8e40bd92a66ad
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.040746777196116336 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.