Block
#22644419
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
277 days ago (Jun-06-2025 08:38:47 AM +UTC)
Transactions:
202 transactions and 91 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.014621809309598119 ETH (0 + 0.051462077758315969 - 0.03684026844871785)
Total Difficulty:
0
Size:
80,802 bytes
Gas Used:
21,087,450 (58.58%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000001747023393 ETH (1.747023393 Gwei)
Burnt Fees:
🔥 0.03684026844871785 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,478.31 / ETH
Hash:
0x4fc37d58aa273c031163cbc7ebe940a5dd9cb64fe3e24a3cbd25a4a7f2dc060a
StateRoot:
0xa145b085f1b8b15e39e904512d7606d2295a4c1d8d7a2dc62fcb20a08dfa2be6
WithdrawalsRoot:
0xd72a1d54a889ad65b6f244fc4931142e7aab71b69d3a964795a6e5d79358b8f5
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x6f8693d01a9f48580be63cf18ca93fca5496a0b74d768cf22666d6b2a8258822
Parent Root Hash:
0x5b124c066fbd3820dcefb9d16c50258508a4830e9f25f69d916c64ae9abb9d05
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x090b6b6c09bb6f3831c87c32b729612119c6d1ef9cae040f78dd1f197ad49816
Randao Reveal:
0xb821e8d64af37d3e5e159f3715d6d15c537e134c8b92e8f4bd62ad1d2772f28724ddec91af457beff9c340024bc3777909cf12a735832258d43589566220e2f76f58b7ec057768e943615383d44250f54539f2cd827aea10d4500b957f4dbc7f
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.014509921408286258 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
393,216 (33.33%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000393216 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.