Block
#20166384
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
622 days ago (Jun-25-2024 04:42:47 AM +UTC)
Transactions:
100 transactions and 31 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.039524748312607084 ETH (0 + 0.082160033051231166 - 0.042635284738624082)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
39,187 bytes
Gas Used:
15,304,697 (51.02%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000002785764706 ETH (2.785764706 Gwei)
Burnt Fees:
🔥 0.042635284738624082 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,393.91 / ETH
Hash:
0xe832a89f63d0d9060f58f7a4f359db6819584960210143e6e7daa466fbb895c2
StateRoot:
0x882784433a2faf987562b3a670df1b2288cc8774e7e2ea847145b45cb325f27f
WithdrawalsRoot:
0xc6bae7016a9395c8f86b97ff60f678c601a538b6ef7db82bad3dea2881a25e21
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf137a2a088c04cd944d2e1c1d90aacd38d83a8c5c22d4397e9096a9a119d7d99
Parent Root Hash:
0xd0182977e3bc22284301017a67d9d6773e6c4486a99ad88879936fdb4f3a465a
Beacon Chain Deposit Count:
1556098
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x839022f063317358f5ea0a059684c0adcd7946b2f219bf6547bc1172dcfca0f3
Randao Reveal:
0xb7e7b06baaf53a486bf22345d02e4b81984ba145761d45d30d6d0bb2d98455f1bd66dd76e088c53c61cc0ef23242bf28190b8a2cfd01212bcad5c2e308a44823dbf4b8175254a5d9384ddc3f4fba0ed880905987f85c90cb294fd5fd5b43b6d8
Proposer Fee Recipient:
0xeBec795c9c8bBD61FFc14A6662944748F299cAcf (Fee Recipient: 0xeBe...Acf)
MEV Reward:
0.050385057798356287 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
393,216 (3 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.