Block
#23337071
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
165 days ago (Sep-11-2025 03:15:11 AM +UTC)
Transactions:
168 transactions and 72 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.012048400901985954 ETH (0 + 0.013684982053207266 - 0.001636581151221312)
Total Difficulty:
0
Size:
56,712 bytes
Gas Used:
11,114,674 (24.75%)
Gas Limit:
44,911,940
Base Fee Per Gas:
0.000000000147245088 ETH (0.147245088 Gwei)
Burnt Fees:
š„ 0.001636581151221312 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$4,461.11 / ETH
Hash:
0x6a4d4019a381f4d1faa86c1dc8fb7b2acef97324f4cec965d523207bc4f7ffd4
StateRoot:
0xa539eabb58f12688ab382be397e948f2d1461354e61b6a02646f9e15984c7992
WithdrawalsRoot:
0x8103353430283c207e66895806d9a8fe27216bb10f78529417308ea9a4e4a06b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x18c435c530786503c2ebfc597e37908d9860def88e480a3448332fdd8bbb4ac6
Parent Root Hash:
0xcd81f73bceaf8630ac633971fa3b5168a67572420ef47dda07644263c96283ac
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x1e75e5859ab8071b57ac355f0225b7b262261e948e6557b96264496e0ad01f18
Randao Reveal:
0xb297251a611f491936229fef859d2a47f4bd95038242832b3f0632f1439ab91c31e6102c0a2b42c8707942e7a45fb4aa0fa5b0f8b03e88fa25f5d5ebcc3a88a88b07fe1b006801c792cdb0b36a33a338b1872c2127cbc40414b6f9002deee276
Proposer Fee Recipient:
0x54c378FE83Ec1565Ef60f7CE094bC17cC8ECF528 (Fee Recipient: 0x54c3...528)
MEV Reward:
0.012156202933788208 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (44.44%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (44.44%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000524288 ETH
Excess Blob Gas:
131,072 (1 blob)
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.