Block
#20241172
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
599 days ago (Jul-05-2024 03:22:47 PM +UTC)
Transactions:
131 transactions and 62 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.040885938819978908 ETH (0 + 0.1716415822947641 - 0.130755643474785192)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
62,474 bytes
Gas Used:
11,756,088 (39.19%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000011122377059 ETH (11.122377059 Gwei)
Burnt Fees:
š„ 0.130755643474785192 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,982.07 / ETH
Hash:
0xdd5c8385dcfdb65dfd201a1d3dbe48b9a692db2416ffa612d5621e6dee4daad1
StateRoot:
0x1f9638cb2112b5c082dd2bf7eaf6c8d5a24f3b7725413fdd0ec9531906739044
WithdrawalsRoot:
0x65743500ce933b9a1ba4298fa961d4238520d6da86802c051590c64c2dcac3e2
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1e395f7111ebae51410965c2f672a505fd65348c11dd644584c08c4c3445655d
Parent Root Hash:
0xe4b34425d9a6ff9a90e4094be4ffb63aa8c4a7a5fb74a77ac3dd0d526b98d7c4
Beacon Chain Deposit Count:
1572113
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x70a66188f7b401f4b6b986db8904ba5f484aa79baa344ea07f9642a54b0f1b90
Randao Reveal:
0xad74c3f491d078919a198dad81fd9f1468c9b0427b2091496e3e5cb0c07acf2c2eff83f0d916bd3bfdca54bbbd1ddeeb08746b2d8925f03cc93b7b8cc3b5069d7799086418b1e4c1d3c4269ce5a9a68da5ba7582fc372e2c44ccf9f6b9c94591
Proposer Fee Recipient:
0x0e171fA2B8853558BC5176F0a489dB896B2DEe70 (Fee Recipient: 0x0e17...e70)
MEV Reward:
0.047866561063063284 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2 Blobs (33.33%)
Blob Gas Price:
5 wei (0.000000005 Gwei)
Blob Gas Used:
262,144 (33.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000000000131072 ETH
Excess Blob Gas:
5,767,168 (44 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.