This page is a small, honest Solana explorer that lives in your browser. You paste something from the chain, it works out what that is, asks public RPC nodes for the data and shows it in plain sections. There’s no signup, no wallet connection and no server of ours in the middle. Use it when you want a quick, neutral check of a payment, a wallet or a token, and hop to a full explorer from the links on every result when you need more.
What you can look up with this Solana explorer tool
You can check five kinds of on-chain objects: transaction signatures, wallet addresses, token mints, programs and slots (blocks). The tool also recognises token accounts, stake accounts and vote accounts and shows the fields that matter for each.
- Transaction signatures: the long base58 string your wallet shows after you send something. Typical signatures are 87–88 characters.
- Wallet addresses: any 32–44 character base58 address, for example a Phantom or Solflare wallet.
- Token mints: the address that defines a token, such as the USDC mint EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
- Programs: executable accounts such as Jupiter, pump.fun or your own deployed program.
- Slots: type a slot number to see that block, or type
latestfor the most recent finalized one.
The cluster selector next to the search box switches between mainnet, devnet and testnet. Mainnet is the default. If you arrived from a link with ?cluster=devnet in it, the tool opens on devnet automatically. Our devnet and testnet explorer guide explains when you need each cluster.
How to check a Solana address or transaction
The short version: paste, press Enter, read the status and balance changes first. Here are the steps in order.
- Copy the item from your wallet or app Most wallets have a "View on explorer" or copy button on each activity entry. Copy the signature or the address, not the shortened version with dots in the middle.
- Pick the right cluster Leave the selector on mainnet for real funds. Switch to devnet or testnet only for test transactions and development work.
- Paste and search Paste into the search field above and press Enter. The tool detects the type on its own, so you never need to choose "transaction" or "address".
- Read the overview card For a transaction, check Status, Block time and Fee. For a wallet, check the SOL balance and the token list.
- Open the detail sections Balance changes, instructions and logs tell you what actually happened. Click any address or slot in the results to look it up next.
- Jump to a full explorer if needed Every result has buttons for the same item on Solscan, Solana Explorer and, on mainnet, Orb.
The URL updates with your query (for example ?q= followed by the signature), so you can bookmark a result or send the link to someone. For a longer walkthrough of reading every field, see our Solana transaction explorer guide.
How input detection works
The tool decides what you pasted from the characters and the length, then confirms with the chain. Solana addresses are 32-byte public keys and signatures are 64-byte Ed25519 signatures; written in base58, they come out at predictable lengths.
Base58 is the text encoding Solana uses for keys and signatures. It leaves out characters that are easy to confuse, namely 0, O, I and l. So if your string contains one of them, it isn’t a valid Solana address or signature, and the tool tells you straight away instead of sending a useless request.
After the base58 check, the rules are simple. A string of 32–44 characters is treated as an address. A string of roughly 80–90 characters is treated as a transaction signature. A number of up to 12 digits, or the word latest, is treated as a slot. For addresses, the tool then fetches the account and looks at its owner program: if the SPL Token or Token-2022 program owns a mint, you get the token view; if the account is executable, you get the program view; stake and vote accounts get their own fields; everything else is shown as a wallet.
What each result section means
Each result is a set of cards. Which cards appear depends on what you looked up, and sections with nothing to show are either hidden or marked as empty.
Transactions
- Status: Success or Failed, with the raw error code if it failed. A failed transaction still pays its fee.
- Fee: the total fee in SOL, with a USD estimate on mainnet. The base fee is 5,000 lamports per signature.
- Priority fee: the part of the fee above the base fee, calculated as total fee minus 5,000 lamports for each signature. It goes entirely to the validator.
- Compute units: how much of the compute budget the transaction consumed. The maximum is 1,400,000 per transaction, so a value near your set limit often explains a failure.
- SOL balance changes: every account whose lamport balance changed, before and after. This is the quickest way to confirm a payment.
- Token balance changes: SPL token amounts that moved, with token names from Jupiter where known.
- Instructions: each top-level instruction with its program name, decoded type (for example
transfer), amounts and the count of inner instructions. - Logs: the program log output, collapsed by default. This is where you find messages like “insufficient funds” or a custom program error.
Wallets and other accounts
- Balance: SOL balance with a USD value at the current price.
- Overview: account type, owner program, whether it is executable, and data size in bytes.
- Token holdings: SPL and Token-2022 balances above zero, sorted by USD value from Jupiter, with a verified badge for tokens on Jupiter’s verified list. Up to 40 holdings are shown.
- Recent signatures: the latest 20 transactions with status, slot and time, plus a Load more button that fetches the next 20.
Programs add the program data account, the upgrade authority (or an “Immutable” badge if there is none) and the last deployed slot. Our program explorer guide explains why the upgrade authority matters before you trust a contract.
Token mints
- Price, market cap, liquidity and holder count from Jupiter on mainnet, plus a verified or unverified badge.
- Supply and decimals read directly from the mint account.
- Mint authority and freeze authority: an address if someone can still mint new tokens or freeze accounts, or a “Disabled” badge if that power has been revoked.
- Top holders: the ten largest token accounts with their share of supply.
- DEX markets: up to six trading pairs from DexScreener, sorted by liquidity, with price and 24-hour volume.
The token explorer guide explains how to read authorities and holder concentration as risk signals.
Blocks
A slot lookup shows block time, block height, parent slot, the number of transactions, the blockhash and the fee reward paid to the leader. The first 25 signatures in the block are listed so you can open any of them.
Tip: an active mint authority isn't automatically a scam, since stablecoin issuers need one to create new coins, but on a fresh memecoin it means the supply can still grow.
Data sources behind the lookup
All on-chain data comes from public Solana RPC nodes; prices and market data come from three public APIs. Nothing is cached or rewritten by us on the way.
On mainnet the tool tries several public RPC endpoints in turn: PublicNode, Solana Vibe Station and the official api.mainnet-beta.solana.com. If one returns a rate-limit or access error, the tool moves to the next automatically. Devnet and testnet use the official api.devnet.solana.com and api.testnet.solana.com endpoints listed in the Solana clusters documentation. The RPC methods are the standard ones, such as getTransaction and getSignaturesForAddress.
Token names, logos, verification status and USD prices come from Jupiter’s public token API. DEX pair data comes from DexScreener’s public API. CoinGecko serves as a fallback for the SOL price. Price data is only fetched on mainnet, because devnet and testnet tokens have no market value.
- Clusters
- Mainnet, devnet, testnet
- Account needed
- No
- Runs
- In your browser
- On-chain data
- Public Solana RPC nodes
- Prices and tokens
- Jupiter, CoinGecko fallback
- DEX markets
- DexScreener
- History per page
- 20 signatures, load more
- Queries stored by us
- None
If you want to build something similar yourself, our Solana explorer API guide compares free RPC methods with paid explorer APIs.
Privacy: what happens to your queries
Your query never touches a Solscanner server. The page’s code runs in your browser and calls the RPC and price providers directly, so we have nothing to log and we don’t log anything.
Two things do stay with you. First, your browser remembers your last six searches in local storage so you can rerun them with one click; the Clear link next to them removes the list. Second, the URL contains your query, which is useful for sharing but means it appears in your browser history. The providers you query (the RPC nodes, Jupiter, DexScreener and CoinGecko) receive your request and your IP address, just as they would if you used any other explorer. Our privacy policy has the full detail.
Limits of a browser-based Solana tx explorer
This tool is deliberately light, and that has costs. The main ones are rate limits, history depth and the lack of labels and exports.
Rate limits. Public RPC nodes are shared and throttled. The official mainnet endpoint allows 100 requests per 10 seconds per IP address and is not meant for production use. A busy wallet lookup makes several requests at once, so if you search many items quickly you may see an error; wait a few seconds and try again.
History depth. Public nodes don’t all keep the full ledger. Recent transactions load reliably, but a signature from years ago may come back as not found even though it exists. Archival explorers handle that better.
No labels, no CSV, no charts. The tool shows raw facts, not “this is Binance’s hot wallet”. It doesn’t export history or draw price charts, and it decodes only standard parsed instructions, so a complex DeFi route shows program names and inner instruction counts rather than a plain-English story.
Freshness. Transactions are read at “confirmed” commitment and blocks at “finalized”, so a transaction sent a second ago can take a moment to appear. At current slot times of roughly 250–300 ms, that wait is short. The live network stats page shows the current slot and TPS.
When to open Solscan, Orb or Solana Explorer instead
Use this tool for quick checks; switch to a full explorer when you need history, labels, exports or developer features. Each result links to the same item on the three explorers below, so switching costs one click.
- Solscan when you need CSV export, token holder lists beyond the top ten, address labels or analytics dashboards. See our Solscan review.
- Orb by Helius when a transaction touches many programs and you want a plain-language explanation, or when you need deep wallet history filtered by time. Read the Orb review.
- Solana Explorer when you work with programs: IDLs, verified builds, Anchor account decoding, instruction simulation or a custom RPC. Our Solana Explorer review covers these tools.
For the full comparison of every major option, including Birdeye for token research and Solana Beach for validators, see our ranking of the best Solana explorers. And if one of those sites is failing to load, the explorer down guide lists alternatives, this tool among them.
By the Solscanner research deskUpdated · Review methodology