ETH Price: $2,301.39 (-4.77%)

Block

#21761889
MEV Block
EigenPhi
Block Height:
21761889
Status:
Finalized
Timestamp:
363 days ago (Feb-02-2025 10:44:59 PM +UTC)
Proposed On:
Block proposed on slot 10976023 , epoch 343000
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.251758107826624275 ETH (0 + 0.673434004055298783 - 0.421675896228674508)
Total Difficulty:
0
Size:
60,240 bytes

Gas Used:
13,297,014 (44.28%)
Gas Limit:
30,029,295
Base Fee Per Gas:
0.000000031712074322 ETH (31.712074322 Gwei)
Burnt Fees:
šŸ”„ 0.421675896228674508 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,869.16 / ETH
Hash:
0x0ef513b7b5d2ea95530510bbfb94551eabd6d245ab80455152fceea4d7796e5b
StateRoot:
0x26f904fde9070885832d93dcfbd0a5dff5cf853da45c33d57fae1412134418d3
WithdrawalsRoot:
0x1961fcbf0b3be681c9640d6c7a0b443bc205ef3c2d6a6aa73409598cbd106a18
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0x5b1ab5f012a715c911bbdb0064f71520a499f48e1aaed3de41a2d00875eb64f0
Parent Root Hash:
0x08860f453190d074445c411c47d018085ced191367a0abce36f0cfb547e01979
Beacon Chain Deposit Count:
1896857
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xc6fd9a169250e12c67be0516424fe8becf57c0805970112ac88e432cd5da3a50
Randao Reveal:
0xb71215f2c4a6e0288e9e53123c0e8ff54af9755a21d199d5688a60db3d4eb0082cd29c30be550b9b9b549f6f0f2d1a0711d56b4b446c145265a4407c8cf991bdbd291534d203e389b6b738daa1b9e1612fa187edb08a3387fb570a0ee67963fb
:
:
:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
0.000000000001129923 ETH (0.001129923 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000888607604736 ETH
Excess Blob Gas:
46,530,560 (355 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.