Block
#22944800
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
225 days ago (Jul-18-2025 08:10:11 AM +UTC)
Transactions:
222 transactions and 71 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.185170942947670029 ETH (0 + 0.263839654545184323 - 0.078668711597514294)
Total Difficulty:
0
Size:
85,320 bytes
Gas Used:
15,393,186 (42.30%)
Gas Limit:
36,388,039
Base Fee Per Gas:
0.000000005110619179 ETH (5.110619179 Gwei)
Burnt Fees:
🔥 0.078668711597514294 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,549.56 / ETH
Hash:
0xc57838c0e4e58c83f8c19915339461289a61234c4bedf1f373f9b35f8cf2bfee
StateRoot:
0xfdf6b245a29605c5411c33864b519ce1f61ac472239271174fbc0c0132a2defa
WithdrawalsRoot:
0x3dfc9054f2e28183a61a0cbc4aad44dbeafd1af052345b18840d92f39195ad70
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xbabae19d7158b4d059820d19922bc10bba3e03b27328372061de333ef6d2ffba
Parent Root Hash:
0x5318ef1c0eefddac2587e9a50c59d79d2cf16bf195031e2eaf0e126aa3c4abd2
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x1059c8b692fc54f7cbc1c8cfaa818b4ead1034b1005b598cedd791d8b6ea12ab
Randao Reveal:
0xa9a5bb710cc3b6106d62fe15a4e9ac559e79ceff73857d5dfb523db72411e1cc3a072699fb3448e3c42aff7e8a981376149795fed139693baa694e538f57170dcb867535a5841398e1d68eaa948d75ce5b79500f67ab5c2ea8e2d4b3bc4de6ce
Proposer Fee Recipient:
0x13F2241aa64bb6DA2B74553fA9E12B713b74F334 (Fee Recipient: 0x13f2...334)
MEV Reward:
0.181494436520814875 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
1.125 MiB (9 blobs)
Blob Utilisation:
9 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
1,179,648 (100.00%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000001179648 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.