Block
#21933180
Status:
Finalized
Timestamp:
362 days ago (Feb-26-2025 09:25:23 PM +UTC)
Transactions:
333 transactions and 152 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.087030803557966241 ETH (0 + 0.140176610765723016 - 0.053145807207756775)
Total Difficulty:
0
Size:
172,392 bytes
Gas Used:
35,980,565 (99.95%)
Gas Limit:
35,999,965
Base Fee Per Gas:
0.000000001477069835 ETH (1.477069835 Gwei)
Burnt Fees:
š„ 0.053145807207756775 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,333.12 / ETH
Hash:
0x9c36c18c5338105e85eb445fbc819a6f07a652192a8307d19c956b02cbf6744a
StateRoot:
0xa21bb127f39da924eadbc67cfe36f9cff24316b58db7e9876e869c88abbfd9d6
WithdrawalsRoot:
0xde4ec6c6a7025ca24aeb14fa669661f252c86d39b8f7020c299081699c4fc4bf
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc0c7b7a65ac848936ec09be93ac2c51d80f4f67aeb11ca98835851e050c78386
Parent Root Hash:
0x98486d8dfd365e90fb4531c75d058381ee56df7849b2ec3c3b8e789db662c691
Beacon Chain Deposit Count:
1930436
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xcf3880f207a34d4bed869e338f12e8c478f89d1018179a9b7467451c71c1b122
Randao Reveal:
0x9259c724f1e83071f56fdd4ed6a6c264bfd6dd886d76ed2b7a96e474971737a6a7a5c0013797b3040ba1f2e8e50022bd10a1f6ecfd366a864ae916bf4bd1355f6e0d524a9a806736669f5199ae590dd2d5db6c9c8c73eede4cb98cd7b8d24bcd
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.083815634747282257 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
0.000000016347630139 ETH (16.347630139 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.012856299465474 ETH
Excess Blob Gas:
78,512,128 (599 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.