ETH Price: $2,031.46 (-2.49%)

Block

#21813691
MEV Block
EigenPhi
Block Height:
21813691
Status:
Finalized
Timestamp:
381 days ago (Feb-10-2025 04:20:23 AM +UTC)
Proposed On:
Block proposed on slot 11028100 , epoch 344628
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.05297302189993298 ETH (0 + 0.06698535796443527 - 0.01401233606450229)
Total Difficulty:
0
Size:
135,578 bytes

Gas Used:
17,752,783 (49.46%)
Gas Limit:
35,894,329
Base Fee Per Gas:
0.00000000078930363 ETH (0.78930363 Gwei)
Burnt Fees:
šŸ”„ 0.01401233606450229 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,661.94 / ETH
Hash:
0x88801d88a3d1618252fbe5c3cb4ef9aedabcb36de3bb1ae568dfe82bb073a9c0
StateRoot:
0x929fd904db6ad822dcd254ebcfac1008997f376b5a6926da7545bcc1d750d577
WithdrawalsRoot:
0x13bcf3afb36347bb6761b0a389fbf028387b9f2bdebd1080b50913682f111380
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0xe53ebf5dba077977ed3e74bd82d79ba42256ca54d67f56db45b3f979ee4774a5
Parent Root Hash:
0x56dd64a1a843c152a2a500f0937c834f2d63d849e252542eb006f718c12eb0d0
Beacon Chain Deposit Count:
1906218
Slot Graffiti:
Block by Stakely.io Lido103 (Hex:0x426c6f636b206279205374616b656c792e696f204c69646f3130330000000000)
Block Randomness:
0x0a5a1ead3a47cb6e887d4198472a1ba54ac588eb7f5eec09be70b08401503f02
Randao Reveal:
0xb5f2f4bedd748de72dc4ba8ad6018f047c4f97d7610bddf509287e63375e9447261295b5b1d6d3776e1c71b7290601a31501d4861d983e3349bfc9006c0f2ae88830a5e5eac99f812d70c8c6ecab211d31a12bdc51cdf24aeff8ffba4959cd32
:
:
:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (66.67%)
Blob Gas Price:
0.000000000000025067 ETH (0.000025067 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000013142327296 ETH
Excess Blob Gas:
33,816,576 (258 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.