Block
#23302083
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
170 days ago (Sep-06-2025 05:49:59 AM +UTC)
Transactions:
176 transactions and 80 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.006966693287090329 ETH (0 + 0.011397163054209689 - 0.00443046976711936)
Total Difficulty:
0
Size:
210,033 bytes
Gas Used:
21,751,160 (48.29%)
Gas Limit:
45,043,944
Base Fee Per Gas:
0.000000000203688896 ETH (0.203688896 Gwei)
Burnt Fees:
š„ 0.00443046976711936 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$4,274.53 / ETH
Hash:
0x3a813745a5e58cf942c215779a54738b88159b811412f99307cb903f83183368
StateRoot:
0xc7c2f3be825813ffcfaf9cdb6c4ef52f47728d69d5bbc55f762189f57eae7d37
WithdrawalsRoot:
0x9ef0e1e3e03078c54c95427bbb4475598936a489788d98b8b549143cc6c83e7a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x29eb6c532e41c80576973292d3ec02d3a93604d0a9dbd4d25840320ac61c1bc5
Parent Root Hash:
0xadd9b3af7abfc5ef28d3d3f3faa2c5bac8df9583e1dad6977d5440aa20bb269f
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x3272988b94f8d72f7de0a5d8e83873265f69738c237a1a83efd69417680e6a19
Randao Reveal:
0x9784e37cb7900525777543bfef9e2557cfded797feb4f07cc9e1487fa069e95cacdb1366797f981d91b21a25323c4deb140b376c3645a164a6b5321b1e2412f0baf6b0584670733c0f50184a0e4fe112694298c05505b5ae1c96a409db8f2937
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.007822039983604323 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:
655,360 (5 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.