Block
#17072755
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1057 days ago (Apr-18-2023 09:42:47 AM +UTC)
Transactions:
113 transactions and 36 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.052679588174265249 ETH (0 + 0.55593646649318832 - 0.503256878318923071)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
64,671 bytes
Gas Used:
11,425,069 (38.08%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000044048476059 ETH (44.048476059 Gwei)
Burnt Fees:
🔥 0.503256878318923071 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$2,104.28 / ETH
Hash:
0x148b2d2f70a2cc62d51bb209fc2c1ba41f2eae9f03f8981f435eaf740edb19b5
StateRoot:
0xd46675db2d904f194c604bb2721736c144b2d91fefa2cc9c992af0e329e57436
WithdrawalsRoot:
0xd2b4e77853464dd5ef592b0c5292ec5f5005bff5bd6f755a356c1ebf5bf8b06a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xdedd3057dbd7a9dfe2debb360c8829036e97a46807a6725bde3bdd342c175d70
Parent Root Hash:
0x41193c4a52ae6dd343963c30f574d33bb9d257c705808d6fea53070794094e2a
Beacon Chain Deposit Count:
596663
Slot Graffiti:
poapqFgrWg9hW8Idd4BhhVcEK+YLMu0A (Hex:0x706f617071466772576739685738496464344268685663454b2b594c4d753041)
Block Randomness:
0xff331676887dad957a644fce81e71543dd561843971ecf9213fd6b6eb41912f6
Randao Reveal:
0x8eaa5a1055b495c7cf864b4264eed3803e76a69e3cc07971de097f45a4e11d1ffbb366cb858a61fcef9da68018d1602619332428713cebcf7686d2c6a1b02f6883ebcec28ee2bd102ce0b868105c66443a2e5484ee10f7c8cde68350bdaa8b75
Proposer Fee Recipient:
0x9f4B4CeCa7aCE96834Bd2fcC961c772De7cb481a (Fee Recipient: 0x9f...81a)
MEV Reward:
0.044146653890520336 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
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.