Why Does Phantom Wallet Show Wrong Token Balance?

Token Balance Display Mechanism

1. Phantom Wallet retrieves token balances by querying the Solana RPC endpoint configured in the user’s settings.

2. It uses the getParsedTokenAccountsByOwner RPC method to fetch SPL token holdings associated with the public key.

3. The wallet does not store on-chain state locally—it relies entirely on real-time RPC responses for balance calculation.

4. If the RPC node is out of sync or returns incomplete account data, Phantom displays stale or missing token entries.

5. Custom token metadata is fetched separately from token-list repositories; mismatches here cause incorrect symbol or decimal rendering.

RPC Node Synchronization Issues

1. Public RPC endpoints like https://api.mainnet-beta.solana.com may experience transient lag during network congestion or validator downtime.

2. Phantom does not validate block height consistency across multiple RPC providers—it defaults to a single configured endpoint.

3. A node that has not processed recent token transfers appears to show zero balance even when transactions are confirmed on other nodes.

4. Some RPC services prune old token account records to conserve storage, causing phantom accounts to vanish from balance queries.

5. Cross-cluster forks—though rare—can lead to temporary balance discrepancies until finality is reached across all validators.

Token List and Metadata Mismatch

1. Phantom pulls token metadata—including decimals, logo, and name—from community-maintained lists such as solana-token-list hosted on GitHub.

2. If a token’s mint address is absent from the list or contains outdated decimals, Phantom misinterprets raw lamport values as tokens.

3. Tokens deployed on devnet or testnet sometimes leak into mainnet token lists, triggering false positive balances in wrong environments.

4. Manual token additions bypass list validation, but incorrect decimal input causes balance scaling errors visible only after transfer confirmation.

5. Duplicate mint addresses registered under different names in overlapping token lists confuse Phantom’s internal mapping logic.

Wallet Caching Behavior

1. Phantom caches token account data for up to 30 seconds to reduce RPC load and improve UI responsiveness.

2. Cache invalidation occurs only on explicit user action—like switching networks—or after timeout, not on-chain event detection.

3. Concurrent wallet usage across devices without session synchronization leads to divergent cached states.

4. Browser extension storage limits may truncate large token account arrays, silently omitting low-balance tokens from display.

5. IndexedDB corruption in persistent storage can lock stale balance snapshots that persist across reloads and restarts.

Frequently Asked Questions

Q: Why does my token balance appear correct on Solscan but wrong in Phantom?Phantom depends on RPC node state and token list accuracy; Solscan may use a different RPC provider or direct ledger parsing, resulting in divergent views.

Q: Can I force Phantom to refresh token balances immediately?Yes—disconnect and reconnect your wallet to the dApp, or manually switch RPC endpoints via Settings > Network > RPC URL to trigger full cache reset and fresh query.

Q: Why do newly received tokens take minutes to appear in Phantom?The delay stems from RPC propagation latency, Phantom’s 30-second cache window, and absence of real-time WebSocket subscription to token account changes.

Q: Does Phantom support custom RPC endpoints with WebSocket subscriptions?No—Phantom exclusively uses HTTP-based RPC calls and does not implement WebSocket listeners for account change events, limiting real-time balance updates.