Block
#23200833
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
185 days ago (Aug-23-2025 02:34:59 AM +UTC)
Transactions:
91 transactions and 71 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.025963474995429128 ETH (0 + 0.033696657943197999 - 0.007733182947768871)
Total Difficulty:
0
Size:
53,547 bytes
Gas Used:
11,887,489 (26.42%)
Gas Limit:
44,999,957
Base Fee Per Gas:
0.000000000650531239 ETH (0.650531239 Gwei)
Burnt Fees:
š„ 0.007733182947768871 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$4,777.18 / ETH
Hash:
0x5256bcd256b16c1be20233239d451cc803cb45b78cf686f2e108c63aa1bf4673
StateRoot:
0x716335f96e391fdf555211203e5b95c0cdff9d227b56053a1af55f30fbb97498
WithdrawalsRoot:
0x09a670b38f227233cd5524c0fedfe380068f7785a572fc5b19fce6ec59944361
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x01fbeb7843c6f0eea1ce01e8319a14d8df7b994621937af617d507b582c41ff8
Parent Root Hash:
0xf619df8c4de59fe743b7cd4336e22087b3def34c8a962c216a945ce8b0d074f1
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x1639dba589d7d07ef5fb6a525426f9abc9477b072339a510b454379d947d83ec
Randao Reveal:
0xa465371d1034f3ec5b021a88160d7cb1879a611280255467746b7e6e89d360484a382c56d7670bf47562c89c35548ccd0a27eba045ccee6901b2c4965f59d4caa4c0ef7ce0966ba05e041b337fd32fa8c8e7ab6bde0ccfb0157423731cafc4c6
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.050890439858722053 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:
786,432 (6 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.