Confirm Which Wallet Account a Website Is Using

A wallet nickname identifies an entry in an interface; the full public address identifies the account being inspected. Before investigating a balance, confirm that the site and your wallet are referring to the same account.

Compare full addresses across three views

Open the intended account in your wallet and locate its full public address. Compare it with the address the site displays and the address opened on the network explorer. Do this comparison privately; there is no need to post the address to complete it. A shortened prefix and suffix can help you recognize an entry, but use the full value when resolving a mismatch.

Distinguish selection from permission

A browser wallet may contain several accounts while exposing only some of them to a website. MetaMask’s provider documentation describes account-change events and permitted account lists; it also warns that account ordering in SDK sessions is not a selection guarantee. That documentation explains why checking the displayed address is useful. It does not prove which provider or event handling RunixCoin uses in every browser.

Investigate a mismatch without moving funds

Suppose the wallet shows Account B while a page still displays Account A. Stop entering quote amounts for a moment. Inspect the site connection details in the wallet, identify the intended account, and compare the page again after using the wallet’s documented account-selection process. Do not transfer funds between accounts merely to make a stale page look correct. If the mismatch persists, record it as an unresolved display or connection problem.

Recheck the network independently

Matching addresses do not settle which chain is being viewed. Compare the selected network and the explorer network after confirming the account. Keep an account mismatch and a wrong-network problem as separate findings: switching a chain is not switching accounts. The RunixCoin public quote remains fixed to Base WETH-to-USDC regardless of other network views. A successful address comparison confirms identity alignment only; it does not verify a balance, ownership, quote or executable route.

References and verification

Reviewed 10 November 2026. Product details reflect inspected interface code; camera scanning, browser behavior and mainnet execution were not verified.