Block
#22617209
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
268 days ago (Jun-02-2025 01:12:47 PM +UTC)
Transactions:
139 transactions and 72 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.026324629369213329 ETH (0 + 0.081476371119773173 - 0.055151741750559844)
Total Difficulty:
0
Size:
60,286 bytes
Gas Used:
13,135,252 (36.49%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000004198757797 ETH (4.198757797 Gwei)
Burnt Fees:
š„ 0.055151741750559844 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,609.07 / ETH
Hash:
0x76576d65188e6ff70b3ff039c8df16289215cf37996e753b21c741dcf2c93b29
StateRoot:
0xe863db7a6fe0fc4eba83db482e25504237e821f0716624dccd333add3748d2a6
WithdrawalsRoot:
0x730e11493f36646fd5953ca404ae1c9bdae644d640fc5ed6a7ad82235fa8c4ea
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xe35ad8ebbb71b93d9a4f25c1b9757dc4743ba9d1feb280ab9fa00c282cff2dc1
Parent Root Hash:
0xbf035df6a745ecf00240cac73cee63542b5b18999ef3d71ba62c76e55663b781
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x83a35c924c9a9138ca7bdb1ff6e465208a90dd1cc0dc6452b37dc17eaa1173c9
Randao Reveal:
0xab9855ffc4ecf0afd7ddbf931fe806f206ed31ec865e368deb09dfab884aac74b29ab3febffc0b5a7e9f5ab7c1f4508908e4f2fa36f389f8f8605b719be694a741b86c850a326d65d44d8f84a297b33052193ceec344db8c97455b3e7865852d
Proposer Fee Recipient:
0x7D16d2c4e96BCFC8f815E15b771aC847EcbDB48b (Liquid Collective: Fee Recipient)
MEV Reward:
0.021503326562055294 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.