Block
#17269668
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1011 days ago (May-16-2023 03:39:23 AM +UTC)
Transactions:
185 transactions and 89 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.55600751508965376 ETH (0 + 1.62612637200509475 - 1.07011885691544099)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
94,845 bytes
Gas Used:
15,539,870 (51.80%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000068862793377 ETH (68.862793377 Gwei)
Burnt Fees:
🔥 1.07011885691544099 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,824.52 / ETH
Hash:
0x371ab34b7f38e68a81f23db469485932fbbb66d60c24bd7596bcd120112d88b2
StateRoot:
0x06f97b215d207433f45772a705fa60c3ee1ca4fa00f279b73e97b2619109fded
WithdrawalsRoot:
0x0b64d0af36caf6e6b50fdc50d5dc6ae7be2be0cf633270a8c6cc41948061269f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf09a7cea01dfc086a2fbc8171ae1a4adb0ef5a315d3753f6cc22dfac5ce1eee5
Parent Root Hash:
0x874c15db60abde4e62577b9f6999173031a415d4f8603e01350fc29094b86e2c
Beacon Chain Deposit Count:
697274
Slot Graffiti:
poapqFgrWg9hW8Idd4BhhVcEK+YLMu0A (Hex:0x706f617071466772576739685738496464344268685663454b2b594c4d753041)
Block Randomness:
0xdfa2174eddc112594b1d832fa361dd5046272caa7cbe691d82d3de441271e964
Randao Reveal:
0xb598666624270cd2863df79596fa5ef73b4612e5111f3568ef35b7a5ad2691ee88f5f1f9854be438a111a6c1d61a40d90bd7e9546a8fa70441121b2b705e28bdbda68714ec2c7b22c731accdb57297d5bbb2029c7cd34b098e089751cf1f20ee
Proposer Fee Recipient:
0x9f4B4CeCa7aCE96834Bd2fcC961c772De7cb481a (Fee Recipient: 0x9f...81a)
MEV Reward:
0.554012676744433848 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.