Block
#20600922
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
562 days ago (Aug-24-2024 08:44:47 PM +UTC)
Transactions:
173 transactions and 78 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.005797045336818668 ETH (0 + 0.018436963817986241 - 0.012639918481167573)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
62,778 bytes
Gas Used:
16,343,511 (54.48%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000000773390643 ETH (0.773390643 Gwei)
Burnt Fees:
🔥 0.012639918481167573 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,769.86 / ETH
Hash:
0xfffa648f6d079c708a86eeeb0f129142d3c5d964e0b48fd0cd2600b66cc8bd5f
StateRoot:
0x5122e76b51a4d4474d9a29544b02f39c0551f259dd4683a54a3ddb3384d4b4a1
WithdrawalsRoot:
0xf9ce1958621252bf796c1c37b6c4ea564e44ef5670f39e6fb25a6d10b9d5db45
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xde46d5a04e69fe73f4bfa9161a84fef839e6246c26cfaad4a5d4856aa3463462
Parent Root Hash:
0xc43a998d074a41cfe235ba900b184c7bb2cae1a957d42f98e5c67e9a25971a4a
Beacon Chain Deposit Count:
1652289
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xdbeda4c6ea4669f0d0cf36cb6f81d1d804edf28dd6eacae0db2a55c6653a4068
Randao Reveal:
0x85687dc73f299d618d2487d8202ba384d3aede19662fca6e56b775b57256dcc2e29588e45a38e2519d0643e80d8a60bd08c16f09de0109ce71e3a4e981bcac81a778768774ed063774334f8f317ec82ed8a88b0bd0edf100b76468616b479717
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.023411866600105993 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:
262,144 (2 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.