Block
#17206004
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1035 days ago (May-07-2023 03:29:11 AM +UTC)
Transactions:
181 transactions and 244 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.306341522214864079 ETH (0 + 2.547353657548238944 - 2.241012135333374865)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
122,572 bytes
Gas Used:
20,388,249 (67.96%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000109916851385 ETH (109.916851385 Gwei)
Burnt Fees:
🔥 2.241012135333374865 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,879.53 / ETH
Hash:
0xdf89454c8e197e16cd846b04ce8ce03aa0fe4b6b06910023a24dff4c11d55707
StateRoot:
0xc0117179b40b098e7f1e1175f8037b6b87b1a0032a3c6ec239a36fa978a4939a
WithdrawalsRoot:
0xd62c6abebc99985b53398ab6399390401b906261a69d647e4cf3b9b69a996aed
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf2bc3be1333cf37da1c2a9e5cbe98c59ba21baccafdaca5d9dcf098584b7d531
Parent Root Hash:
0xca877f46526d5f474f91ad7950f959eef8aa026c224f986897574a7f944f87fa
Beacon Chain Deposit Count:
656278
Slot Graffiti:
poapqFgrWg9hW8Idd4BhhVcEK+YLMu0A (Hex:0x706f617071466772576739685738496464344268685663454b2b594c4d753041)
Block Randomness:
0xccd8e5bcad0fa4c5ddc5aaa26d94d1e543215ba13a45ccdf761d39f7266c624c
Randao Reveal:
0xa083b9c98ac59394ac3856eb9d244b4f804f33ec1b29d5b9fa8fb5e2328a7957ad5665019cbb406a31537d797b23e572173f5aed1133ba5a36d5940cbd843d40f87d252ca18dd40da9c991f767683cae6cb05a4afa5573047d26cc80a28c9d6d
Proposer Fee Recipient:
0x9f4B4CeCa7aCE96834Bd2fcC961c772De7cb481a (Fee Recipient: 0x9f...81a)
MEV Reward:
0.312831570561927429 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.