Block
#20195922
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
616 days ago (Jun-29-2024 07:42:11 AM +UTC)
Transactions:
202 transactions and 53 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.015204900441949254 ETH (0 + 0.040234035761059494 - 0.02502913531911024)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
52,511 bytes
Gas Used:
11,663,088 (38.88%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000214601273 ETH (2.14601273 Gwei)
Burnt Fees:
🔥 0.02502913531911024 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,373.52 / ETH
Hash:
0x5519970e4a239a70ccec0744e85ae26f0a2b1de600d934d1d9ed487fca1f24f9
StateRoot:
0xbec666e06f4e0e7c1df34a1f250a2aa4b38f9eecc11fc613ec577c049795e06b
WithdrawalsRoot:
0xea14a3efef6557fb25e50bbaf55240e51aca725ed0bcbcd1e68e4d0b72e751b7
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xa0356466aa1c8c0abc72a7308b516890f807e5ab48930ffcb87bb88a96b03ab2
Parent Root Hash:
0xd20240d20c9edb1eabecf7a162cca9ad21276765dac3358474408b1ac1942c52
Beacon Chain Deposit Count:
1564436
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x2d5f12c3829fe48aef74d5636de5e26c1061a137ef082bbe599e30af6ff5f353
Randao Reveal:
0x99f9124d37c2587791955c5fd8fb48bac0dab76600dd7dec60e9130eb9822b457de798258a96ce4d54754daf507d3f6004a61b97331e031d3493ea71be85f3a233fb762ec98059b2b785e6eb5f9fcab2c1577cf6f2855d3fd55ca439524668b5
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.016495715676415126 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000000000065536 ETH
Excess Blob Gas:
131,072 (1 blob)
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.