Why Solflare Doesn’t Show Your Balance: Troubleshooting RPC Connection Issues

By ELINA VASILIEVA | March 18, 2026

A user has installed Solflare, created or imported a wallet, and sees no SOL balance, no token list, and no transaction history despite knowing funds are present on the Solana blockchain. The interface loads normally. The wallet address appears correct. But when they check a blockchain explorer, the account clearly holds assets. The problem is almost always not the wallet itself, but the connection between Solflare and the Solana network—specifically, the RPC node that the wallet queries to retrieve account data.

This scenario is more common than it appears, and it reveals a critical distinction in how browser-based wallets work. Solflare cannot generate balances from thin air; it must connect to an RPC endpoint to fetch account information. When that connection fails, times out, is rate-limited, or points to an unreliable node, the wallet displays nothing even though your funds exist. Understanding why this happens and how to fix it requires knowing what an RPC connection is, why it matters, and how to configure it correctly.

Understanding RPC: The critical link between wallet and blockchain

RPC stands for Remote Procedure Call. In the context of Solana and Solflare, it is the protocol that allows your wallet to ask a server, “What is the balance of this account?” or “What tokens does this wallet hold?” Without a functioning RPC connection, the wallet cannot retrieve any data from the blockchain. It can still hold your private keys securely and allow you to construct transactions offline, but it cannot display readable information about your assets.

Solflare ships with a default RPC endpoint, usually maintained by a public infrastructure provider. This endpoint is free and meant to work for most users, but it is also shared by thousands of other wallet users, applications, and services. When traffic is heavy, the default endpoint may be overloaded. When Solana experiences congestion or network issues, the endpoint may fall behind. When it reaches rate limits, it begins rejecting requests. None of these failures mean your wallet is broken or your funds are lost. They mean the connection is not working at that moment.

The second critical point is that an RPC endpoint is just a server answering questions about the blockchain. It does not hold your private keys. It does not control your funds. If the default endpoint goes offline entirely, your wallet still exists, your recovery phrase still works, and your SOL and SPL tokens are still on the blockchain. You would simply need to connect through a different RPC endpoint to see them again. This separation of concerns—your keys and your data queries—is why RPC configuration is often the actual solution to a missing balance problem.

Different RPC endpoints can also have different levels of support for advanced features. Some provide full historical data and support all Solana RPC methods; others are lighter-weight and may not. A wallet trying to fetch complex data through a limited endpoint may time out or return partial information. Even if the endpoint is working, if it is behind the chain tip, it may show stale balances or old transaction histories. Checking your account on a blockchain explorer like Solscan or Solana Beach can tell you quickly whether the funds are actually there; if they are, an RPC issue is almost certainly the cause of the mismatch in your wallet.

Why the default RPC endpoint fails more often than expected

Solana’s default public RPC endpoints have become a victim of their own utility. Because they are free and widely advertised, they attract enormous traffic. A single popular dApp or trading bot can generate thousands of requests per second. When a wallet extension like Solflare queries the default endpoint for balance updates, it is competing for bandwidth with thousands of other simultaneous requests. Congestion is nearly inevitable during peak hours, especially when Solana experiences network activity spikes or mempool congestion.

Rate limiting is another common culprit. RPC providers implement rate limits to prevent any single source from monopolizing resources. These limits are usually expressed as requests per second or per minute. If Solflare, combined with other dApps you have open in your browser, makes too many requests in too short a window, the endpoint may start rejecting calls. The wallet user sees a timeout or a blank balance and assumes something is wrong, when in fact the endpoint is working correctly—it is just saying “not right now.”

Endpoint reliability also varies based on infrastructure. Some public endpoints are hosted on robust, globally distributed infrastructure with failover and redundancy. Others run on more modest hardware or single locations. If a provider experiences an outage or a connection drop, their endpoint becomes unreachable. Solflare will wait for a response until it times out, which can feel like the wallet is frozen. During that wait, nothing is broken; the wallet is simply waiting for an answer that is not coming.

The timing of when you use the wallet also matters. Early morning or late night tends to have lower traffic and more stable connections. Mid-morning or afternoon, especially on weekdays when centralized finance markets are active, can see significantly higher congestion on public endpoints. Similarly, any news of issues on the Solana network itself—validator problems, network slowness, or unexpected forks—drives up RPC traffic as users rush to check their balances, which makes the bottleneck worse.

Diagnosing RPC problems before changing anything

The first diagnostic step is to confirm that your funds are actually on the blockchain. Open Solscan.io or Solana Beach, paste your wallet address into the search box, and view your account in a blockchain explorer independent of Solflare. If the explorer shows your correct balance and all your tokens, the issue is definitively not your wallet or your keys. It is a connection problem. If the explorer also shows no balance, then either you have the wrong wallet address, you are on the wrong network (mainnet vs. devnet), or your funds were never there.

Next, check Solana network status. The official Solana Status page and the community-maintained Solana Beach status dashboard report on validator health, network congestion, and known issues. If the network is experiencing problems, many RPC endpoints will be affected simultaneously. In this case, switching endpoints may help, but the core issue is network-wide, not specific to one provider.

Then, reload Solflare. A simple refresh of the browser tab may reset the connection and allow the wallet to retry its RPC calls. If the balance appears after a refresh, the issue was a transient timeout or a rate limit that has now cleared. If it still does not appear, proceed to changing the RPC endpoint. You can also check your browser’s developer console (F12 in most browsers, then the Console tab) to see if there are error messages related to network requests. Errors mentioning “429” (rate limit), “timeout,” or “connection refused” point toward an RPC connectivity issue.

One more check: verify that your browser extension has permission to make network requests. Solflare requires network access to function. If your browser settings or a privacy extension is blocking outbound connections from the wallet extension, it will not be able to reach any RPC endpoint. Temporarily disabling other browser extensions and checking Solflare’s permissions in your browser settings can help isolate whether a blocker is the problem.

How to configure a custom RPC endpoint in Solflare

To access Solflare’s custom RPC configuration, open the wallet extension and navigate to Settings (usually a gear icon or menu option). Look for a section labeled “RPC Provider,” “Network,” or “Endpoint.” Most wallet interfaces allow you to either select from a list of known RPC providers or enter a custom endpoint URL manually. The important thing is that you can make this change without restarting your browser or losing access to your wallet.

When selecting a replacement RPC endpoint, several options exist. Alchemy, QuickNode, Helius, and Triton RPC are commercial providers that offer free or paid tier RPC endpoints specifically for Solana. Many of these services have better uptime, lower latency, and higher rate limits than the default public endpoint. To use them, you typically sign up for a free account, create an application, and receive an endpoint URL. You then paste this URL into Solflare’s custom RPC field.

If you prefer not to sign up for an account, the Solana Foundation maintains a list of public RPC endpoints operated by community members and organizations. Visiting this list and trying an alternative public endpoint can sometimes resolve the issue if the problem is specific to one provider rather than Solana-wide. Keep in mind that public endpoints without a commercial backing may be less stable or have lower rate limits, but they are still a valid option to test.

After entering a custom RPC endpoint, save the setting and reload the wallet. Solflare should now query the new endpoint instead of the default. If you see your balance appear, the custom endpoint is working. If not, try a second endpoint to rule out that particular provider having problems. It is also worth testing the endpoint URL directly in a browser tab to confirm it is responding. For example, pasting a URL like `https://api.mainnet-beta.solana.com` into your address bar should return a JSON response confirming that the endpoint is live.

Choosing between free and paid RPC providers

Free RPC endpoints are zero-cost but come with trade-offs. They are usually rate-limited more aggressively, have higher latency, and may not support all Solana RPC methods. They work fine for checking balances and sending transactions, but if you are using advanced features like batch transactions or historical data queries, a free endpoint might time out. They are also more prone to outages because they often run on minimal infrastructure.

Paid RPC providers like Alchemy or QuickNode charge per request or offer tiered subscription models. In return, you get higher rate limits, better uptime guarantees, faster response times, and full support for all RPC methods. For casual Solflare users who just want to check their balance and send a transaction occasionally, a free endpoint is usually adequate. For active traders, developers, or anyone connecting to multiple dApps simultaneously, a paid provider is often worth the cost because you avoid the frustration of timeouts and connection drops.

A practical middle ground is to start with a free endpoint and switch to a paid one only if you encounter persistent problems. You can also try multiple free endpoints from different providers before committing to a paid service. Some users maintain a list of several working endpoints and rotate between them if one becomes congested. This is not ideal from a convenience standpoint, but it is effective and costs nothing.

It is also worth noting that when you download Solflare wallet, the extension comes pre-configured with a sensible default, but that default is not necessarily the best endpoint for your situation. Your geographic location, your ISP, your browser, and the time of day all affect which endpoint will perform best for you. Experimenting with one or two alternatives can often identify a significantly faster and more reliable option than the default.

What Solflare Custom RPC Configuration actually controls

Understanding what the RPC setting does and what it does not do is crucial to avoiding confusion. The RPC endpoint controls which server Solflare queries for balance information, token data, transaction history, and account metadata. It does not control the security of your private keys, which remain encrypted locally in your browser and never leave your device. It does not affect your ability to sign transactions offline or your ability to recover your wallet using your seed phrase. Changing the RPC endpoint is purely a data-fetching mechanism; it has no impact on the cryptographic security of your wallet.

The RPC setting also does not determine which network you are on. Solflare distinguishes between Mainnet (the production Solana network where real assets exist), Devnet (a test network), and Testnet (another test network). You must select the correct network independently of the RPC endpoint. It is possible to have the right RPC endpoint but the wrong network selected, in which case your balance would still be blank because you are querying the wrong blockchain entirely. Always confirm you are on Mainnet before assuming there is an RPC issue.

The RPC endpoint is also independent of any hardware wallet integration. If you are using Solflare with a Ledger device for enhanced security, changing the RPC endpoint does not affect the Ledger connection. The Ledger stores and signs transactions; the RPC endpoint simply fetches data about your account from the blockchain. Both must work correctly together, but they are separate systems.

Testing a new RPC endpoint and verifying it works

After entering a custom RPC endpoint, the test is simple: does your balance appear? If it does, the endpoint is working and connected to the blockchain. If it does not, wait a few seconds and reload the wallet once more. Sometimes an RPC endpoint takes a moment to respond on first connection. If the balance still does not appear after a reload, try a different endpoint or revert to the default and attempt the diagnostic steps again.

A useful secondary test is to send a small test transaction while connected to the new endpoint. If the transaction succeeds and you see it appear in your transaction history within a few seconds, the endpoint is working correctly. If the transaction hangs or fails, the endpoint may be having issues even if it initially displayed your balance. This is rare but possible; some endpoints may retrieve data but fail to broadcast transactions reliably.

For users who want deeper verification, a curl command or a tool like Postman can test an RPC endpoint directly without going through Solflare. For example, running `curl -X POST -H “Content-Type: application/json” -d ‘{“jsonrpc”:”2.0″,”id”:1,”method”:”getBalance”,”params”:[“YOUR_WALLET_ADDRESS”]}’ https://api.mainnet-beta.solana.com` will return your balance in lamports (the smallest unit of SOL, with 1 SOL = 1 billion lamports). If this command returns your correct balance, the endpoint is working, and any remaining issue in Solflare is either a caching problem or a browser-specific issue rather than an RPC connectivity problem.

Once you have confirmed that a new endpoint works, consider bookmarking it or saving it as your default. If you use Solflare frequently, a reliable endpoint will save you from repeated troubleshooting. Different endpoints may perform differently depending on your location and time of day, so do not be afraid to change it again if you encounter slowness later.

When RPC issues indicate a deeper problem

In rare cases, a persistent inability to connect to any RPC endpoint, even after trying several different providers, may indicate a problem beyond the endpoint itself. A network issue on your ISP, a firewall rule blocking cryptocurrency traffic, or a browser configuration problem could prevent Solflare from connecting to any external server. Testing with a different browser or on a different network (such as a mobile hotspot) can help determine whether the issue is specific to your current setup.

Similarly, if you can see your balance but transactions consistently fail to broadcast, the problem may not be the balance-fetching RPC endpoint but rather a different endpoint or service used for transaction broadcasting. Some RPC providers offer separate endpoints for data queries and transaction submission. Solflare usually handles this automatically, but if you are using a less common provider, it is worth checking the provider’s documentation to ensure both services are available and working.

For users experiencing issues with NFTs not showing in Solflare’s integrated gallery despite owning them on the blockchain, the RPC endpoint is less likely to be the culprit. NFT display depends partly on indexing services that catalog token metadata, which is separate from the RPC query. However, a slow or unreliable RPC endpoint can delay metadata loading, making it appear as though NFTs are missing when they are simply loading slowly. A faster endpoint often speeds up NFT gallery display as well.

If switching RPC endpoints, reloading the wallet, and checking the blockchain explorer confirm that your funds are present but Solflare still shows no balance, the issue may be specific to your wallet instance. Exporting your private key or seed phrase, removing Solflare entirely from your browser, reinstalling it fresh, and importing your wallet again can sometimes resolve corrupted wallet state or cached data issues. Always ensure you have a safe backup of your recovery phrase before uninstalling any wallet extension.