Block
#22917401
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
224 days ago (Jul-14-2025 12:24:59 PM +UTC)
Transactions:
245 transactions and 76 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.025253438452403202 ETH (0 + 0.108747334895858394 - 0.083493896443455192)
Total Difficulty:
0
Size:
93,325 bytes
Gas Used:
17,243,166 (47.57%)
Gas Limit:
36,244,833
Base Fee Per Gas:
0.000000004842144212 ETH (4.842144212 Gwei)
Burnt Fees:
š„ 0.083493896443455192 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,014.66 / ETH
Hash:
0x7ac561339ba03067e2339c53fcd9ef8b3027a671160e2eaee78b7867e6ef7d62
StateRoot:
0xa5452b19b65ddf7a5dca4538a8ed9ae15da35636e2e4e7c77c25a9dcd5cf1d3d
WithdrawalsRoot:
0xc1e48454de46196b457bc396e4ff8e6f33afda5fdd86a2fd91fe3c82787d2b4d
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x0e5935c5ebac06c9bceecb284f812425d6f7e40fcbcfc14660c9f2dce2084781
Parent Root Hash:
0xd2085da1e5b2bf53cdb0a5efc22e8966b117cf913adb57f7b3566dccef867671
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xa4abca640aad3fcedfcb28891ed1b2b47be26cab09cb9e5a876fb77234a22b38
Randao Reveal:
0x970ad0a7c8f3c4e27ef0e1c9e9dbd7a758d9f1eebd5d90622581ad0e4bb7f29658a670e9513fe067cb59b24623f532c30b5a27176cc2be8e17280cf8adcf931fe00befc3009ca512c7303af8047d654eed399f3dcead9e065fe8cdd20d7b54c4
Proposer Fee Recipient:
0x7D16d2c4e96BCFC8f815E15b771aC847EcbDB48b (Liquid Collective: Fee Recipient)
MEV Reward:
0.022518161649183721 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.