Block
#20092738
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
619 days ago (Jun-14-2024 09:29:23 PM +UTC)
Transactions:
125 transactions and 64 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.054903517152981703 ETH (0 + 0.238385089247551396 - 0.183481572094569693)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
57,995 bytes
Gas Used:
13,866,687 (46.22%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000013231824739 ETH (13.231824739 Gwei)
Burnt Fees:
š„ 0.183481572094569693 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,479.74 / ETH
Hash:
0x9b33cc9c9e9449020272052570e880568672102db1921972a5bd293795afbee0
StateRoot:
0x736c9398919926d9b0ca56d76de0dd6f32817d37a5bafc49d22854e3e5ef8d8b
WithdrawalsRoot:
0x18fbe9937706564e0582adfcbaa78383553b51f9c551ea12e91fed243a3a2da8
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf8e18f7d8f5fdaa57e8d614bb902975341d10237ea77df9e2c9372713a767c20
Parent Root Hash:
0xba8bcbce7f5191a487cce66bec1d3582a6d0bd4d5d48576957178346268bdeeb
Beacon Chain Deposit Count:
1537748
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x350deca6c4bde7104ef9632ad0f7278dd43029363e2d164cb8de75ca157e8487
Randao Reveal:
0x8b4b51541b3762411fda2010c028afc8fdef58ae7c47cc53219e8ac4505d23d6c960d5c3c2c2b79776fc65bf16ae565d0a24522eb79d8eb1a8730fd9ddb7dfcfc81b5b4ed843479132dbf4332d437b998360bcab6bac5e70c4b0717324a2bc04
Proposer Fee Recipient:
0x2194331af2cF9dE9Adb36cf09654faD65cafb58b (MEV Builder: 0x219...58b)
MEV Reward:
0.360348014499627784 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000131072 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.