Block
#20195226
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
618 days ago (Jun-29-2024 05:22:23 AM +UTC)
Transactions:
191 transactions and 61 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.0138151246484516 ETH (0 + 0.048956050223822145 - 0.035140925575370545)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
93,976 bytes
Gas Used:
17,332,385 (57.77%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000002027472017 ETH (2.027472017 Gwei)
Burnt Fees:
🔥 0.035140925575370545 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,373.52 / ETH
Hash:
0xda092177df51c04e7168f1b36a20504e367cf3357c86a1aed1b38735ebedd829
StateRoot:
0x19bd9521a0cfb952122ec81c455775b84fffd8d3fec034e32340e9400c0c3f9d
WithdrawalsRoot:
0xc8fce4e0850ca7f0cc621a74894cb6832fbbb1184db20243622cad9f62bb9c35
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb2f65c7fb5320d3567a8bfc7e08aab0c0ddbf1871d0e54acf8af024a2f8912f5
Parent Root Hash:
0x766a3d007eff8f24ffb3b010c9f4b06bccc0304e891630c8bf65984a659d6964
Beacon Chain Deposit Count:
1564436
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xc7a83c4b39ee2da3fec22624632fa72582dfe82521f5f0f510b979e498e7520d
Randao Reveal:
0xa43e12d15b18c13a656f5b85d45f12d1e0bb7def531ebce28c69e51b654e1bd24f812e8c09c114c0cbed8e4429b3459b0ef6cef9db91a55d89dd67c6c1df534cbbac81537ef90babaf669e3c1562f1dfcc877cd42d5f4d53cb99cbd73f7ed850
Proposer Fee Recipient:
0x0077732907bFC6208933Cfd2a51aFB8f33cA5958 (Fee Recipient: 0x0077...958)
MEV Reward:
0.013400207887743584 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:
1,572,864 (12 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.