SolstackBlog
← All guides

Account Inspection / General Dev Education

How to Inspect Any Solana Wallet or Token Account (No Code Required)

What a wallet or token account address alone tells you, how to tell what kind of account you're looking at, and how to read the fields that matter.

2026-10-09·6 min read·Verified against mainnet-beta
How to Inspect Any Solana Wallet or Token Account (No Code Required)

Anyone can read any Solana address in full, whether it's a wallet, a mint, a token account or a program. All you need is the address. There's no API key, no code and no special access. This post covers what you'll find and how to read it.

First work out what kind of account it is

A 32-byte address doesn't tell you what it is, so start there. Almost every address you'll look up is one of these:

  • Wallet. An ordinary address controlled by a keypair. It holds SOL, and token accounts can belong to it.
  • Mint. The account that defines a token: its supply, decimals and authorities. It isn't any one holder's balance.
  • Token account. One holder's balance of one mint. A wallet has a separate token account for each token it holds.
  • Program. Executable code. Its owner field points to the loader that deployed it.
  • PDA (program derived address). An address created so that no private key exists for it, which lets a program own accounts. Understanding Solana PDAs explains them.

The account's owner field (the program that controls it) and the layout of its data tell you which type it is. A wallet, for example, is owned by the System Program and has no data apart from its SOL balance.

What a wallet address tells you

You get its SOL balance. Its tokens live in separate token accounts, so a plain lookup of the wallet won't list them. To see them you query the token accounts it owns. History matters too. A wallet with a balance and no transactions is often a newly generated address. One with years of activity behind it tells you much more about who you're dealing with.

What a mint address tells you

  • Supply, the total amount that exists, in the token's base units.
  • Decimals, how many base units make one displayed token.
  • Mint authority and freeze authority, and whether each is live or revoked (None). These are the most important trust signals on a mint. Revoking mint and freeze authority explains why.

If the mint has on-chain metadata, either Metaplex or Token-2022's on-mint format, you can also read its name, symbol and logo URI.

What a token account tells you

It shows which mint it's for, which wallet is its owner, and its current balance. It also shows whether the account is frozen, which only happens if the mint's freeze authority has used that power on it.

What a program address tells you

You can see whether it's executable and which loader deployed it. The loader matters for upgradeable programs, which have an upgrade authority. A program account doesn't hold much readable state itself. The interesting data usually sits in separate accounts the program owns, often PDAs derived from the program's address.

An empty result doesn't mean the address is wrong

A valid address with no account on the current cluster is unused. It may be newly generated, or it may exist on a different cluster. Looking on devnet when the account is on mainnet, or the other way round, is the most common reason for a "not found" result. Check which network you're on before deciding the address is wrong.

Account Inspector works out what kind of account an address is and shows the fields that matter for that type, so you don't need to know beforehand whether it's a wallet, a mint or a program. The Account Inspector docs have the details.