Increase coin query limit to 10000 in BalanceResolver #653
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated the BalanceResolver to fetch up to 10000 coins instead of 2500. This allows for handling larger datasets in a single query.
Summary
The reported issue was valid at the time of report. The UTXO
0xca44...0002existed on-chain but was not displayed in the Explorer. The issue self-resolved when the user ranconsolidateCoins, which spent the UTXO.Investigation Findings
1. Indexer Status: ✅ Working Correctly
0xca44f9aedd67551ccc2cec1610c633a1b133d3493be12edf6ac7dfad4fc84eb1was properly indexedtransactions_accountswere created correctly2. UTXO Lifecycle
0x0f648407461f4bae9fa8d759d692459b00a261596a664d6c9b3f6a2e2d1fdc223. At Time of Report (Nov 18, ~5:12 PM)
4. Resolution
User ran
consolidateCoinsat ~5:43 PM, which spent the UTXO and created new consolidated UTXOs. Explorer then displayed correctly.Root Cause
Unable to confirm definitively. The UTXO was returned by fuel-core but not displayed by Explorer.
Ruled out:
Possible causes (unconfirmed):
Actions Taken
Preventive measure: Increased UTXO display limit from 2,500 → 10,000
Recommendations
Monitor - If similar issues recur, use diagnostic tools to capture state before it self-resolves
Frontend investigation - If reproducible, check React Query cache configuration and CDN caching headers
No immediate code fix required - Issue was transient and self-resolved
Status: Closed - Cannot Reproduce
Issue was real but no longer reproducible. Root cause unconfirmed. Preventive measures added.
Checklist