Block
#22133818
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
333 days ago (Mar-26-2025 09:37:35 PM +UTC)
Transactions:
223 transactions and 73 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.011956599027902918 ETH (0 + 0.018681518670084578 - 0.00672491964218166)
Total Difficulty:
0
Size:
89,138 bytes
Gas Used:
17,742,948 (49.29%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000000379019295 ETH (0.379019295 Gwei)
Burnt Fees:
š„ 0.00672491964218166 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$2,009.64 / ETH
Hash:
0xbb8ff713ababa768c921b9ba48b2621c6ca1455f9341cca77993ad6c5a07bf70
StateRoot:
0xdeac286374c1df3192e06190cfc65abf2a4519dd3f79e19c7f17b1a426e00480
WithdrawalsRoot:
0x13fa7c090c00bae11e859a553f6f8d7e8adb331eab0b529e630d719f7ea0ab30
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd48018b8949ddebd3ebd57c7a28a1463b73947e2e14fdd20db38c0649676c8c0
Parent Root Hash:
0x250c1dc35d81908c8a050f75274d7033796bf9c4d677202fdfdcdb63db6f8fd6
Beacon Chain Deposit Count:
1987720
Slot Graffiti:
Twinstake (Hex:0x5477696e7374616b650000000000000000000000000000000000000000000000)
Block Randomness:
0xfdb05add214abcfc4e0426eaf664bcb6c41075b0b1d816140cdd53d5bb761e24
Randao Reveal:
0x938be5aa8ccb86322c3adbb39ae08220e077f0730a2908c1247afcaed4fcdaaa68f78cb50917772db50413e431699c9b11f3a5dab4130464524dcc0e0c9847fbb632741961d1b4b588d0e154f735eeecddd75e0c35b7f094cbc30125a44ac41d
Proposer Fee Recipient:
MEV Reward:
0.031549803705564038 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
0.000000000002477798 ETH (0.002477798 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000324769939456 ETH
Excess Blob Gas:
49,152,000 (375 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.