Block
#17734313
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
983 days ago ()
Transactions:
186 transactions and 58 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x333...203 in 12 secs
Block Reward:
0.070120928346326992 ETH (0 + 0.719000907295960522 - 0.64887997894963353)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
60,060 bytes
Gas Used:
24,208,515 (80.70%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000026803791102 ETH (26.803791102 Gwei)
Burnt Fees:
š„ 0.64887997894963353 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,891.68 / ETH
Hash:
0xf208e980b8fadcbce160a93f09087c54420c4ad68bf14443de219b37739ac882
StateRoot:
0x92ff653413d70a6642bdf8fe37b658f4085955d05e15755571a771b6c7f54a64
WithdrawalsRoot:
0x03c07db269b22d5f75a63e9aa0fd1f47eb2f8a752505be86a4b5356fb2d5f1ad
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x9736a50fd4452d4b5c65f86bc6570a9bbf3bafdf19533a08190142e24ad15462
Parent Root Hash:
0x30cef8ccc465f1d58a9391f54c379dc81fbba2a93114755f9020f7af75d86308
Beacon Chain Deposit Count:
867112
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x7f7f9a340fe7481159dea58f320a70f5bb3f946a96824cf64a8c0903a9edab66
Randao Reveal:
0x99ba1f4890640cd219d32f1c3ca995e1a32972cac73e5497fd82b4ce727ff280ce191e4c484fd2ed49ca7daad1ac592507bcbd345ea942a679635b90a4278739f41382c38e81414244a2afe436c418216f84b3e960569f67bf9e11c2b0fb60db
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.136159580329742509 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.