Skip to content

Conversation

@nelitow
Copy link
Contributor

@nelitow nelitow commented Dec 18, 2025

Updated the BalanceResolver to fetch up to 10000 coins instead of 2500. This allows for handling larger datasets in a single query.

  • Closes FE-1776

Summary

The reported issue was valid at the time of report. The UTXO 0xca44...0002 existed on-chain but was not displayed in the Explorer. The issue self-resolved when the user ran consolidateCoins, which spent the UTXO.


Investigation Findings

1. Indexer Status: ✅ Working Correctly

  • Transaction 0xca44f9aedd67551ccc2cec1610c633a1b133d3493be12edf6ac7dfad4fc84eb1 was properly indexed
  • Block 38178780 with 9 transactions was indexed
  • Account links in transactions_accounts were created correctly
  • All 4 outputs including the 88.625B UTXO were stored

2. UTXO Lifecycle

Event Block Timestamp
Created 38178780 Nov 17, 2025 11:49
Spent 38296564 Nov 18, 2025 20:32
Spending Tx 0x0f648407461f4bae9fa8d759d692459b00a261596a664d6c9b3f6a2e2d1fdc22

3. At Time of Report (Nov 18, ~5:12 PM)

  • Brandon's direct fuel-core query confirmed UTXO existed
  • Explorer was not displaying it
  • Account had ~50 UTXOs total (well under display limits)

4. Resolution

User ran consolidateCoins at ~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:

  • ❌ Indexer failure (transaction was indexed correctly)
  • ❌ UTXO limit (account had only 50 UTXOs, limit was 2500)
  • ❌ Blockchain state (fuel-core had the UTXO)

Possible causes (unconfirmed):

  • Frontend/CDN caching of stale data
  • Transient rendering issue
  • Network response handling edge case

Actions Taken

Preventive measure: Increased UTXO display limit from 2,500 → 10,000


Recommendations

  1. Monitor - If similar issues recur, use diagnostic tools to capture state before it self-resolves

  2. Frontend investigation - If reproducible, check React Query cache configuration and CDN caching headers

  3. 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

  • I've added error handling for all actions/requests, and verified how this error will show on UI. (or there was no error handling)
  • I've reviewed all the copy changed/added in this PR, using AI if needed. (or there was no copy changes)
  • I've included the reference to the issues being closed from Github and/or Linear (or there was no issues)
  • I've changed the Docs to reflect my changes (or it was not needed)
  • I've put docs links where it may be helpful (or it was not needed)
  • I checked the resulting UI both in Light and Dark mode (or no UI changes were made)
  • I reviewed the entire PR myself (preferably, on GH UI)

Updated the BalanceResolver to fetch up to 10000 coins instead of 2500. This allows for handling larger datasets in a single query.
@vercel
Copy link

vercel bot commented Dec 18, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
fuel-explorer-v2-vite Ready Ready Preview Dec 19, 2025 5:46pm

@cursor
Copy link

cursor bot commented Dec 18, 2025

PR Summary

Increase coins query page size in BalanceResolver.utxos from 2500 to 10000.

Written by Cursor Bugbot for commit 49fdc68. This will update automatically on new commits. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant