Every Solana explorer, tested and explained

A Solana explorer is the first tool most people open after they send SOL, swap a token or mint an NFT, and the last one a developer closes before shipping a program. This site exists because picking the right Solana block explorer for the job saves real time: one explorer is best for holder lists, another explains a messy DeFi swap in plain English, a third is the only sensible choice for devnet. Below you’ll find how explorers work on Solana, which one to open for which task, and a map of every guide and review on Solscanner.

What is a Solana block explorer?

A Solana block explorer is a website that queries Solana nodes and shows the raw ledger as readable pages: one page per transaction, account, token mint, program and block. It is read-only. It cannot move your funds, sign anything or reverse a payment.

Under the hood, every explorer calls the same kind of RPC methods that wallets use. When you paste an 88-character signature, the explorer runs something close to getTransaction and renders the status, fee, signer, instructions and balance changes. When you paste a wallet address, it asks for the SOL balance, the token accounts owned by that address and the list of recent signatures. What separates a good explorer from a bad one is everything on top of those calls: decoding program instructions into words, labelling known addresses, attaching USD prices, filtering spam and keeping deep history available.

If you’re completely new to this, start with our beginner guide on what a Solana explorer is and how to read one. It walks through a real transaction page field by field.

Why a Solana explorer differs from an Ethereum explorer

Solana explorers look similar to Etherscan at first glance, but they solve harder display problems because the chain is faster, stores state differently and packs more work into each transaction. Four differences matter most.

Speed and volume

Solana produces a new slot roughly every 250–300 milliseconds since SIMD-0525 started cutting the old 400 ms target in 50 ms steps during August and September 2026. The network processes about 4,000–4,300 transactions per second including validator votes, and roughly 1,400–1,800 non-vote transactions per second in our own measurements. An explorer has to index all of that and still answer your search in under a second. That is why history depth varies so much between explorers, and why a brand-new transaction can take a moment to appear on one site while another shows it instantly.

The accounts model

On Ethereum, a token balance lives inside the token contract. On Solana, everything is an account: a 32-byte address that holds lamports, data and an owner program. Your USDC is not stored “in” your wallet; it sits in a separate token account owned by the SPL Token program, linked to your wallet and to the USDC mint. A good Solana blockchain explorer hides this by grouping token accounts under the wallet that owns them. A weak one shows you a list of unfamiliar addresses. The guides further down explain how to read balances, mints and holders through this model.

Versioned transactions and address lookup tables

Solana transactions have a hard size cap of 1,232 bytes and can reference at most 64 accounts. To fit complex DeFi routes into that space, version 0 transactions can load extra account addresses from on-chain address lookup tables. For an explorer, that means an account list is not complete until the lookup tables are resolved. Explorers that handle this well show every account a swap touched. Older tools, or ones that request only legacy transactions, can fail to load them at all.

Compute units and priority fees

Every Solana transaction pays a base fee of 5,000 lamports per signature, half burned and half paid to the validator. On top of that, a sender can set a compute unit price, and the priority fee equals that price times the compute unit limit, divided by one million. The default budget is 200,000 compute units per instruction and the maximum is 1,400,000 per transaction. A useful Solana network explorer shows compute units consumed next to the fee, so you can see whether a failed transaction ran out of budget or was simply outbid. The Solana fee documentation has the full formula.

Which Solana explorer should you use for each job?

Short answer: Solscan for everyday lookups and exports, Orb for readable history, Solana Explorer for developers and test clusters, Birdeye for token trading data. The table maps common jobs to the explorer we’d open first. Scores come from our 2026 explorer ranking.

Two notes on the table. SolanaFM once led on human-readable transactions, but it was acquired by Jupiter in September 2024 and several widgets stayed on “Loading” in our September 2026 test, so read our honest SolanaFM status review before relying on it. And if you only need a quick check and don’t want to pick at all, our own tool fetches the data directly from the chain.

Our explorer reviews: seven tools, one test routine

Each review on Solscanner follows the same routine: we paste the same set of signatures, wallets, token mints and programs into every explorer, then score speed, token data, readability and developer tools. The widget above shows the resulting scores; the reviews explain them.

Solscan and the official explorer are the two names most people compare, so we wrote a dedicated head-to-head: Solscan vs Solana Explorer shows where each one wins and when to keep both tabs open. The remaining reviews cover Birdeye (8.7), OKLink (8.0), Solana Beach (7.6) and SolanaFM (7.2). Each has a verdict box, pros and cons, and screenshots of the pages you will actually use.

Our opinion after months of daily use: no single Solana explorer website does everything best. Most experienced users keep Solscan as the default, open Orb when a transaction touches five programs and they need to know what really happened, and switch to the official explorer whenever they work on devnet or need to trust the source.

Guides: reading transactions, wallets, tokens, NFTs and DeFi

The guides section answers “how do I check this?” for each type of on-chain object. Each guide owns one topic, so you can go straight to the page you need.

Transactions come first because that’s what most searches are about. The Solana transaction explorer guide shows how to confirm a payment, read each instruction, and diagnose a failed or “not found” transaction step by step. For addresses, the wallet guide covers balances, token accounts and full transaction history, including why some explorers hide spam transfers.

For tokens there are two pages. The token explorer guide explains supply, decimals, mint and freeze authority, holder concentration and the red flags that often come before a rug pull. The verified token mint addresses list gives the real mints for USDC, USDT, BONK, JUP, PYTH, WLFI and others, because fake tokens with identical names and logos are common. The real USDC mint, for example, is:

EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v

Collectors should read the Solana NFT explorer guide, which covers ownership history, metadata updates, Candy Machine mints and where to find floor prices, since classic explorers don’t always show them. Traders get their own page on DeFi and DEX explorers: pair explorers such as DexScreener, trading terminals like Photon and GMGN, and how to trace a swap across liquidity pools. The same page explains why a pair explorer and a block explorer answer different questions.

Network, validator and developer pages

The technical half of the site is for people who run, build on or stake with Solana. These pages go deeper than a typical block explorer Solana tutorial and link to official documentation wherever possible.

Developers usually start with the program explorer guide. It covers how to find a program’s upgrade authority, read an Anchor IDL, and check verified builds, which the official explorer pulls from OtterSec’s verification API. If you’re testing before mainnet, the devnet and testnet explorer page lists the right URLs and cluster switches, plus the free public endpoints such as https://api.devnet.solana.com. For code that needs explorer-style data, our explorer API comparison weighs free RPC methods like getSignaturesForAddress against paid explorer APIs, including Solscan’s Lite plan at $49 per month.

Stakers and node operators should read the validator and staking explorer guide, which compares validator dashboards and explains commission, delinquency and rewards. Our live Solana network stats page shows current TPS, slot, epoch progress, supply and validator count. At our last check there were 688 vote accounts, 676 current and 12 delinquent. If you trade memecoins or care about MEV, the Jito bundle explorer guide explains bundles, tip accounts and the 1,000-lamport minimum tip.

Two smaller pages cover specific situations. When your usual explorer won’t load, what to do if a Solana explorer is down lists alternatives and status pages. And for identity and compliance use cases, our Solana Attestation Service page explains how attestations appear on-chain and which explorer shows them today. Filing season has its own guide too: exporting Solana transactions for tax covers CSV exports, historical USD values and cost-basis gaps.

The live lookup tool: a Solana explorer in your browser

Our lookup tool is a small Solana explorer that runs entirely in your browser. You paste a signature, wallet, token mint, program or slot number, and it fetches the data from public RPC nodes, with no account and no server storing your query.

It detects the input type from its length and format. A base58 string of 32–44 characters is an address; 87–88 characters is a transaction signature; a plain number is a slot. Transactions show status, fee, priority fee, compute units, SOL and token balance changes, instructions and logs. Wallets show SOL balance, SPL token holdings with USD values from Jupiter, and recent signatures. Token mints show supply, mint and freeze authority, top holders and DEX markets. You can switch between mainnet, devnet and testnet.

Paste a signature or wallet into our lookup tool when you want a quick, neutral answer. For deep history, labels or CSV export, the result page links straight to Solscan, Solana Explorer and Orb for the same item.

How we test Solana explorers

We test every Solana explorer against the same fixed set of real mainnet items, then score four areas: speed, token data, readability and developer tools. Scores are editorial and updated when an explorer changes in a way that affects users.

In practice that means timing searches for signatures and addresses, checking whether balance changes and token transfers are decoded correctly, comparing holder lists and prices against a second source, and checking devnet support, IDLs, verified builds and API documentation. We also record ownership and maintenance status, because an explorer that stops updating becomes risky: prices go stale and new program formats stop decoding. That’s the main reason SolanaFM sits at the bottom of our list despite its good design.

We don’t accept payment for rankings, and we name the owner of each tool (Etherscan for Solscan, Helius for Orb, the Solana Foundation for Solana Explorer, OKX for OKLink, Staking Facilities for Solana Beach, Jupiter for SolanaFM). Our full testing methodology lists the test items and the weight of each score. Where we quote a network figure, we either link the official source, such as the Solana accounts documentation, or measured it ourselves on public mainnet RPC and say so.

Getting started with a Solana explorer in three steps

If you’ve just landed here with a signature in your clipboard, this is the fastest path.

First, decide what you’re holding. An 87–88 character string is a transaction signature; a 32–44 character string is an address, which could be a wallet, a token mint or a program. Second, open the right tool: our lookup tool or Solscan for a quick check, Orb if you need to understand what a complicated transaction did, or Solana Explorer if you’re on devnet. Third, read the status and balance changes before anything else. A green “Success” with the right amount leaving your wallet and arriving at the recipient answers most questions. If it says “Failed”, the fee was still charged and the logs usually tell you why.

From there, use the guides above for deeper questions. The official Solana transactions documentation is worth bookmarking too, especially if you want to understand why signatures, blockhashes and account limits work the way they do.