Block
#21874177
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
342 days ago (Feb-18-2025 03:32:59 PM +UTC)
Transactions:
111 transactions and 28 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.012371945736609965 ETH (0 + 0.025966024458851318 - 0.013594078722241353)
Total Difficulty:
0
Size:
34,045 bytes
Gas Used:
7,786,789 (21.80%)
Gas Limit:
35,719,620
Base Fee Per Gas:
0.000000001745787477 ETH (1.745787477 Gwei)
Burnt Fees:
š„ 0.013594078722241353 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,670.43 / ETH
Hash:
0xeb37d5861a59df1fbf2b167fde1d9a00e42822110c939ae1b0b54518c3d9b593
StateRoot:
0xc2bfedc2ffd5609c4d5828f6cc3f47bed0728d145661eee706752d1061f8de64
WithdrawalsRoot:
0x4a77d43e28e6dc7e92ba9e8ea3f5462765e7019a7bf34e22c536d90634f7685b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf1dfc668e17917d2a38c944c9e9fa68c1d427ad0037e7e82ad685c48ad13a9b1
Parent Root Hash:
0x95cba2ec88e4f9eed30736d57df51d82484ec154b53100e19d7472b33d415b88
Beacon Chain Deposit Count:
1917711
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x7569f04e3b3557cb48554458b3b97f51cae75babc7a5eb76b92ee37962569c0d
Randao Reveal:
0x80f6bb17bb9a46c93459ebb6d64fedbfa0a4c7d3f215c5f516517de1140a0f90f6375628098121e94494a3be82fde87511568c272fc76aa9fd3ecec933ae147692c1e0cb68376b4e5825045b160782000ef5e0ebb79761d87dc655e52ae5ca58
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.029043977577591965 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
0.000000016347630139 ETH (16.347630139 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.010713582887895 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.