fix incorrect usd fee error when sending usdc

[JustinBeBoy]

Close #3457

This PR:

• fix incorrect usd fee error when sending usdc.
• Add a polling-based scanner with block-range chunking to retrieve transaction history.

Screen Shot:

• USD fee:

• Transaction history

before:

after:

[peterzen]

LGTM. Thank you for working on this @JustinBeBoy .

[JustinBeBoy]

LGTM. Thank you for working on this @JustinBeBoy .

There's still an issue regarding the transaction history that I'm trying to resolve.

[JoeGruffins]

Looks good. I notice there is a usd price here for the base coin but not for the token. Under Amount. Can you try to fix it too?

[JustinBeBoy]

Looks good. I notice there is a usd price here for the base coin but not for the token. Under Amount. Can you try to fix it too?

Let me fix it.

[JoeGruffins]

I'm not sure the transactions not showing up is a bug. Will put more on the issue.

[JoeGruffins]

As @martonp said on the issue, we might not be able to get the incoming transactions. If you just fix the amounts with this pr it's fine. Maybe a note in the UI about not showing incoming transactions if you are ok with making that. Don't worry about it too much as may be impossible currently.

[JustinBeBoy]

Looks good. I notice there is a usd price here for the base coin but not for the token. Under Amount. Can you try to fix it too?

I've researched this issue, and it might not be a bug, but rather that rate sources could be disabled or failing (network error, API rate limit), hiding the USD element. It seems that stablecoins like USDC might not be supported by all APIs.

[JoeGruffins]

I've researched this issue, and it might not be a bug, but rather that rate sources could be disabled or failing (network error, API rate limit), hiding the USD element. It seems that stablecoins like USDC might not be supported by all APIs.

Ok no big deal. If it's not a bug just leave it.

[JustinBeBoy]

@JoeGruffins please help me review and test it.

[Copilot]

Pull request overview

This PR fixes a bug where the USD fee estimate was calculated incorrectly when sending USDC or other token assets. The issue occurred because tokens pay transaction fees in their parent asset (e.g., USDC on Polygon pays fees in MATIC), but the USD conversion was incorrectly using the token's fiat rate instead of the parent asset's rate.

Key Changes:

• Fixed USD fee calculation to use the parent asset's fiat rate and unit info when sending tokens
• Added polling-based transaction history scanner (per PR description, but not visible in provided diffs)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.