Block
#22551508
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
269 days ago (May-24-2025 08:27:59 AM +UTC)
Transactions:
137 transactions and 62 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.042769908507669788 ETH (0 + 0.04809511098249404 - 0.005325202474824252)
Total Difficulty:
0
Size:
66,565 bytes
Gas Used:
12,729,572 (35.36%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000000418333191 ETH (0.418333191 Gwei)
Burnt Fees:
🔥 0.005325202474824252 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,530.92 / ETH
Hash:
0xf5e0eff0b4c67b908213a825c13a7130ecf5c2b578491b7fd8defb44ea4f27cc
StateRoot:
0x434d4438f3d225acf3ce6a1f04f7deb70b39bb0ac148dbd5627a11545d810085
WithdrawalsRoot:
0x8de4cc99800af35cc9fd1d2752fe9de94d29358039534e1f25eb7aab82fce8dc
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd0c5d48ac86d14e6a75a9eba0348626ec8cee472a21464da2b0c84e7ac2a2598
Parent Root Hash:
0xaecc46aafef9bc65c9ed649f7a0ffb0f0415ecc5d512c5a6338dd7b693d32bf2
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xaf72af6d6f7e4cdb04b6b07e72dddfc1bc5b0dfc93d6108553fd2778f88aa05c
Randao Reveal:
0xb2b9c325b24506d059d49bf8474378e9f430317c1701a7b9abee396bc290868b031ddbafad892581f4f4905cb02f36740b5c6cb01fb28818dce65423eaf7ea47d5327fd3be1403f214e260117b884f3ac596a94a4ecb61d24098fde9bc9138a5
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.04181627342540563 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (66.67%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
0 (0 blobs)
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.