Block
#21857600
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
392 days ago ()
Transactions:
92 transactions and 76 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x25B…b43 in 12 secs
Block Reward:
0.007107629503568691 ETH (0 + 0.014762638340164791 - 0.0076550088365961)
Total Difficulty:
0
Size:
72,974 bytes
Gas Used:
10,812,550 (30.09%)
Gas Limit:
35,929,691
Base Fee Per Gas:
0.000000000707974422 ETH (0.707974422 Gwei)
Burnt Fees:
🔥 0.0076550088365961 ETH
Extra Data:
Ty For The Block (Hex:0x547920466f722054686520426c6f636b)
Ether Price:
$2,661.59 / ETH
Hash:
0xbc98105241cf21a913b2f574b9100fe902291cf85c4faafea809fcd5651bb9ef
StateRoot:
0x06212300b24e869acd47cad124ac6f30db85a2a260e185bbf728f273a1d0c756
WithdrawalsRoot:
0xb40731e0b9c872753d25df517b18575680330e6efa4867ebd0a8aacdb810e6c2
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x96c9a45e579ead3640db5e7812d9373c32b8187842d05245e1158912f3225f1a
Parent Root Hash:
0x472e27e0e75f3c8e3e76de5b8acb32c68b5a9e6b941c5a1d588ca87f478f5a66
Beacon Chain Deposit Count:
1914899
Slot Graffiti:
charon/v1.2.0-d60eb93 TK23GEeb (Hex:0x636861726f6e2f76312e322e302d6436306562393320544b3233474565620000)
Block Randomness:
0x4ac374ce6523a13366fac941493ee1768796c2393f20e1539c74430e300fe2b3
Randao Reveal:
0xaea3566c25db5bdaf9abae8fa6e4c2fa333af246c908e62b8bf8eaab223c0687736f8f043af403a4f3bbd153e0dd466f116ed80b1d7caf887bd0c38879898fba73a5ff763aca63119f1b1a4fabe0810c2ac805f067c8962977634381c80494c8
Proposer Fee Recipient:
MEV Reward:
0.017594771614870998 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
5 wei (0.000000005 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000000000393216 ETH
Excess Blob Gas:
5,373,952 (41 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.