Block
#20386193
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
590 days ago (Jul-25-2024 09:17:11 PM +UTC)
Transactions:
172 transactions and 70 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.045918442249599293 ETH (0 + 0.093532634179231231 - 0.047614191929631938)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
71,547 bytes
Gas Used:
16,330,319 (54.43%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000002915692702 ETH (2.915692702 Gwei)
Burnt Fees:
🔥 0.047614191929631938 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,174.48 / ETH
Hash:
0xa08f5b96d948689b250c3624847840b5660f46b8929ed5dfbbe96f38dcb16b4d
StateRoot:
0xfcf7da626c67c511526b2641110dfc1fcb7edd0f536f7d1888e1c6ee604a1fa4
WithdrawalsRoot:
0x36dd09e791a050323329d7187d39b744ad048659d5e75a32adf62a5e30fc2aca
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5af14e330fad27f480475cde393db19d9a57702cf58815607a30bdb93fc03c6b
Parent Root Hash:
0x24c35299522b9481e9a4d5967137d487658fcc607e982ec1da787a8e49169d30
Beacon Chain Deposit Count:
1607923
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x6659f372bbcbf12b5bef685ed31146968f4dfdd48ad140bf60ee29ce0e3ddd5a
Randao Reveal:
0x8ee84da0c2d0a05ab779431ed1a6930eaa5e54b793e4afc5d2b91cbb899424415a93425b9983854fdd5d7734be88a86514695c9ae88347681778fe9b1aebe451b7101f400a4c2c73a34a90fc08573d612748f9e633ed3b6eb58313745dd2d8e4
Proposer Fee Recipient:
0xaCA98383f1262AFbA2b9702D763f6B3fA7288887 (Fee Recipient: 0xaCA..887)
MEV Reward:
0.054050890503413779 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
262,144 (33.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000262144 ETH
Excess Blob Gas:
2,228,224 (17 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.