Solscan
Solscan wallet lookups display accounts that may store data or executable code.
Updated on
Solscan wallet lookups display Solana accounts, which can hold SOL, store data, or contain executable program code. An address alone does not establish that its record represents a personal wallet. Account balances describe holdings, token mint addresses identify assets, and program records explain deployed software. Program and data accounts can also hold SOL, so a balance alone does not distinguish these roles. An account overview supplies holdings and activity context, while a program record adds deployment information and details about interactions with the code.
In short: A SOL balance measures holdings; executable status identifies a program account, while upgrade authority concerns permission to update its code.
Wallet Use, Stored Data, and Executable Code
Wallet use is one context for an account, alongside the storage and software functions that Solana applications need. Solana distinguishes executable program accounts from non-executable data accounts using the executable flag. These descriptions concern an account's function; finding a balance does not settle that classification.
Addresses Used for Wallet Holdings
An account overview brings together holdings and activity associated with an address. Its information can include SOL, tokens, NFTs, stake accounts, balance changes, and funding information. Ordinary wallet accounts are owned by Solana's System Program; this ownership identifies a program, not the person using the address.
Accounts That Store Data
Solana applications use accounts to hold information, so an address lookup can concern application data. Storage alone does not establish that the account contains executable code. The owner field identifies the program permitted to modify the account's data.
Program Code at an Address
Programs supply executable code for decentralized exchanges, lending protocols, staking platforms, and other Solana applications. A program ID identifies a deployed program. With loader-v3, the executable program account points to a separate program data account that stores the compiled code.
Can a SOL Balance Identify a Personal Wallet?
A SOL balance alone cannot establish that an address represents a personal wallet, because Solana's account model also supports data and program functions. The balance answers how much SOL the account holds. On a Solscan program page, the Executable field reports execution capability separately from the SOL balance.
Program Identity Within an Account Lookup
A program record links a program ID with transactions, instructions, and interacting accounts.
Code and Interacting Accounts
An interacting account belongs to the context of a program's activity; interaction alone does not establish that the account contains executable code. A list of participating addresses can therefore include records with different functions.
Transaction details supply context for a particular interaction by identifying the accounts and programs involved. Instructions, inner instructions, and program logs provide deeper execution information. These details help explain what an address did within the recorded transaction, rather than assigning the same function to every address involved.
Deployment and Upgrade Authority
A Solscan program page can include an upgrade authority. That information concerns authority over program updates. An authority shown for a program does not identify the controller of every account interacting with it.
Interface description language (IDL) data can add information about a program's interface when available.
What Separates a Token Holding From a Token Identity?
A token holding concerns assets associated with an account, while token identity concerns which token those assets represent. Solana tokens are identified by their mint addresses. A token page provides asset-level context, including available supply, authority, and holder information. An account overview provides address-level holdings context. Names and symbols can repeat, so a familiar label cannot resolve the token's identity by itself.
Record Choices for an Address Lookup
- If the question concerns SOL or token holdings, use the account overview and its balances; those figures describe assets associated with the address.
- If the executable flag is false, examine the account's owning program and stored data to understand its role; it is not an executable program.
- If the address identifies a deployed program, use its program record to examine interactions and available deployment or authority information.
- If the question concerns which token an account holds, compare mint addresses; matching names or symbols can refer to different tokens.
Public Records and Wallet Control
Account classification explains a record's role; it does not identify a person or certify that deployed code is safe. Public searches do not require a wallet connection. Looking up an address therefore remains separate from authorizing an asset movement, and the explorer does not control the assets it displays.
The account overview suits a question about holdings because it groups balances and address activity. The program record suits an examination of deployed software because it supplies program interactions and deployment context.
What readers ask about Solscan
Can I Use a Transaction Signature in Place of a Wallet Address?
A transaction signature identifies a transaction, while a wallet address identifies an account. When Solscan has indexed the transaction, searching its signature shows the execution result, participating accounts, programs, and balance changes. Searching an account address provides the broader holdings and activity context for that address. A signature alone does not prove that the transaction was processed or confirmed.
How Does an account's Portfolio Value Differ From Its SOL Balance?
The SOL balance states an amount of SOL, while portfolio value provides valuation context for the displayed holdings. An account page can show token holdings alongside its native SOL balance. Read the balance when the question concerns the amount of SOL at the address; use portfolio information when the question concerns the value of its displayed assets.
Does Every Program Page Include Verified Source Code?
A program page does not necessarily include verified source code or security information. Those details appear when available, alongside program information such as transactions, instructions, deployment details, and interacting accounts. Missing source code does not turn the record into a wallet account, and the program classification alone does not establish whether its code is safe.
Which NFT Details Distinguish a Holding From a Copied Name or Image?
An NFT's mint and collection addresses provide identity checks beyond its displayed name or image. Names, artwork, and other metadata may come from external sources, so visual branding alone does not establish which asset an account holds. An NFT record may also show the current owner and transaction history, adding context for that particular asset.
What Does a Validator Result Add Beyond a Balance Lookup?
A validator result adds network-operation and staking context that a balance alone does not provide. It may include a validator identity, vote account, activated stake, commission, current status, and epoch performance. These fields concern the validator's operation and delegation activity.