Block Explorers
A block explorer is how you independently verify what actually happened on-chain, without trusting your own application code or a wallet's summary of events. This tutorial covers why explorers matter, the metrics they expose, the categories of explorer tools available, and what makes each of the popular ones worth reaching for.
Why Use a Solana Explorer?
An explorer reads the exact same public data your RPC calls do - it just decodes and renders it for a human instead of returning raw JSON. That makes it the fastest way to check your own work, and the only practical way to check anyone else's.
Core Use Cases
- Tracking/Verifying Transactions - Paste a signature (tx hash) to see status, success/failure, fees, timestamps, and full details.
- Looking Up Accounts/Wallets - View balances, activity history, and holdings for any public key.
- Exploring Tokens & NFTs - Search by mint address or name to inspect metadata, supply, and activity.
- Analyzing Blocks - Check specific slots for included transactions, leaders, and rewards.
- Program/Smart Contract Inspection - View deployed programs, their interactions, and IDL data.
- Network & Validator Monitoring - Assess overall health, staking, or node performance.
- Debugging & Research - Trace fund flows, DeFi interactions, or historical events.
Common Metrics & Data Points Available
- Transaction Details - Status (confirmed/failed), slot/block time, fee (base + priority), compute units used, inner instructions, logs, balance changes, and token transfers.
- Account/Wallet Metrics - SOL balance, token holdings (with amounts and values), NFT portfolio, transaction count/history, stake accounts, and activity heatmaps.
- Token Metrics - Mint/supply, holders distribution, price charts (where available), trading volume, metadata (name, symbol, logo), and transfer history.
- NFT Metrics - Collection details, ownership, rarity traits, sales history, and listings.
- Block Metrics - Leader/validator, transaction count, rewards, compute unit stats, and timestamp.
- Network-Level Stats - TPS (transactions per second), fee averages, active addresses, TVL in major protocols, and validator performance (APY, delinquency).
- Advanced Views - Parsed vs raw data, fund flow visualizations, program calls, and search filters (by time, address, token, status).
Most explorers (e.g., Solscan, the official Explorer, SolanaFM, Orb) provide these basics with varying depth in UI, speed, decoding quality, and extras like APIs or AI summaries. They serve as the primary way to independently verify on-chain activity beyond what your wallet shows you.
What Is a Solana Explorer?
If you've read Wallets & Explorers, you've already used one - that page's working example builds an explorer.solana.com link for a transaction signature. An explorer is simply a website that queries RPC endpoints on your behalf and presents the results as searchable pages instead of raw JSON.
There is no single official source of truth beyond the chain itself. Every explorer, including the one Solana Foundation runs, is a third-party lens on the same underlying data - which is exactly why cross-checking a surprising result on a second explorer is a reasonable habit, not paranoia.
Key Terms
| Term | Plain-language meaning |
|---|---|
Signature / tx hash | The unique identifier for a transaction, pasted into an explorer's search bar to look it up. |
Slot | A single, roughly 400ms window in which one validator may produce a block - the base unit explorers use for "block" views. |
Indexer | The backend service an explorer runs to pre-process and search chain data faster than raw RPC calls allow. |
Parsed instruction | A decoded, human-readable view of an instruction, as opposed to its raw byte data. |
TVL | Total Value Locked - the combined dollar value of assets deposited in a protocol, a common network-level metric. |
Delinquency | A validator status meaning it has stopped voting on the chain, usually surfaced on validator/network explorers. |
Main Types of Solana Explorers (as of 2026)
1. General-Purpose / All-in-One Explorers
Comprehensive tools for transactions, accounts, tokens, NFTs, programs, and basic analytics. Most user-friendly for everyday lookups.
Top popular ones:
- Solscan - Most widely used community favorite; detailed wallet/token views, NFTs, APIs. solscan.io
- Solana Explorer (Official) - Ground-truth reference by Solana Foundation; clean and reliable. explorer.solana.com
- SolanaFM - Next-gen with strong transaction decoding, diagrams, and network stats. solana.fm
- Orb (by Helius) - Fast, readable, modern interface focused on speed. orbmarkets.io
- OKX Link - Multi-chain explorer with solid Solana support. oklink.com/solana
2. Specialized / Advanced Analytics Explorers
Focus on deeper insights like MEV, validator performance, inner instructions, or developer debugging.
Top popular ones:
- Solana Beach - Strong on validator/network health, telemetry, and staking data. solanabeach.io
- XRAY - Plain-English transaction rendering and detailed decoding.
- Jito MEV Explorer - Specialized for MEV bundles and searcher activity.
- Others like Helius dashboards or niche tools for compressed NFTs/programs.
3. Validator / Network Monitoring Explorers
Primarily for node operators, staking, and ecosystem health metrics - fewer broad consumer options here than in the other two categories.
Main options:
- Solana Beach (as above) - Leading for validators.
- Official Solana metrics tools or integrations built into general-purpose explorers.
- Validator-specific dashboards, e.g. via Solana CLI or community tools.
Notes: Solscan is the default "go-to" for most users, similar to Etherscan on Ethereum. Use multiple explorers for cross-verification on complex transactions. Many offer APIs for developers. Data reflects 2026 ecosystem trends.
Key Metrics & Features by Explorer (2026)
Solscan - most popular general-purpose (solscan.io)
- Comprehensive wallet analytics: balances, token/NFT holdings, transaction history, stake accounts, transfer heatmaps, and portfolio monitoring.
- Detailed token & NFT intelligence: pricing, holder distributions, market data, metadata, reputation/safety checks, and analytics charts.
- Advanced transaction decoding with summaries, instruction logs, fee breakdowns, and DeFi activity tracking.
- Powerful filtering/search across accounts, programs, tokens; robust public APIs for developers.
- Network stats, validator info, and broad ecosystem coverage (tokens, blocks, programs).
Solana Explorer (Official) (explorer.solana.com)
- Ground-truth protocol-level data: raw blocks, transactions, accounts, and cluster switching (mainnet/devnet/testnet).
- Reliable for verifying basic transaction signatures, slot/block details, and core Solana mechanics.
- Simple, lightweight interface for quick lookups without extra analytics layers.
SolanaFM (solana.fm)
- Advanced transaction visualization: diagrams, inner-instruction decoding, and clear summaries for complex DeFi calls.
- Network statistics and dashboards (e.g., true TPS, fee trackers, stablecoin metrics, launchpad overviews).
- User-friendly wallet and asset views with net worth estimates and structured data.
- Strong for debugging and understanding program interactions.
Orb (by Helius) (orbmarkets.io)
- Speed & historical queries: fast lookups, reverse chronological search, time-based filters, and transaction heatmaps.
- AI-powered explanations: human-readable summaries of transactions and tokens.
- Rich block/token/wallet insights: leaders, compute units, program IDLs, markets data, and validators.
- Modern filtering (by time, status, programs, spam) and developer-friendly tools.
Solana Beach (solanabeach.io)
- Validator & network health focus: stake metrics, APYs, vote performance, delinquency, and telemetry.
- Real-time ecosystem monitoring for node operators and stakers.
Other notes: Users often cross-reference explorers - Solscan for daily use, then SolanaFM or Orb for a deeper dive when something looks off. Features like APIs, DeFi/NFT dashboards, and MEV tools (e.g., Jito) further differentiate them for traders, developers, and analysts.
Step-by-Step Walkthrough
Step 1: Get a signature or address to look up
Every explorer lookup starts from one of three things: a transaction signature, a public key (wallet, token mint, or program), or a slot number. The devnet workflow examples in this guide already produce all three.
solana transfer <RECIPIENT> 0.001 --allow-unfunded-recipient --output json | jq -r .signatureStep 2: Build the explorer URL for your cluster
Every explorer needs to know which cluster you mean - the same signature exists independently on devnet and mainnet-beta, pointing at completely different transactions (or nothing at all).
function explorerUrl(kind: "tx" | "address", value: string, cluster: "devnet" | "mainnet-beta" = "devnet") {
const clusterParam = cluster === "mainnet-beta" ? "" : `?cluster=${cluster}`;
return `https://explorer.solana.com/${kind}/${value}${clusterParam}`;
}
console.log(explorerUrl("tx", "YOUR_SIGNATURE"));Step 3: Check the same result on a second explorer
Different explorers run different indexers, so a transaction that looks broken on one can simply be a lagging indexer, not an actual failure. Solscan uses the same ?cluster=devnet pattern as the official Explorer.
function solscanUrl(kind: "tx" | "account", value: string, cluster: "devnet" | "mainnet-beta" = "devnet") {
const clusterParam = cluster === "mainnet-beta" ? "" : `?cluster=${cluster}`;
return `https://solscan.io/${kind}/${value}${clusterParam}`;
}
console.log(solscanUrl("tx", "YOUR_SIGNATURE"));Step 4: Confirm what the explorer shows against raw RPC data
An explorer's summary is a convenience, not a source of truth by itself - for anything your code depends on programmatically, verify against the RPC response directly.
import { createSolanaRpc } from "@solana/kit";
const rpc = createSolanaRpc("https://api.devnet.solana.com");
const tx = await rpc
.getTransaction("YOUR_SIGNATURE", { encoding: "json", maxSupportedTransactionVersion: 0 })
.send();
console.log("Explorer says confirmed; RPC error field:", tx?.meta?.err);Step 5: Reach for a specialized explorer only when you need it
General-purpose explorers cover the vast majority of day-to-day lookups. Reach for a specialized one - Solana Beach for validator health, Jito's explorer for MEV bundles - only when the question you're answering is specific to that domain.
Putting It Together
// explorer-links.ts - build multi-explorer links for the same signature
type Cluster = "devnet" | "mainnet-beta";
function buildExplorerLinks(signature: string, cluster: Cluster = "devnet") {
const clusterParam = cluster === "mainnet-beta" ? "" : `?cluster=${cluster}`;
return {
official: `https://explorer.solana.com/tx/${signature}${clusterParam}`,
solscan: `https://solscan.io/tx/${signature}${clusterParam}`,
solanaFm: `https://solana.fm/tx/${signature}${cluster === "mainnet-beta" ? "" : `?cluster=${cluster}-qn1`}`,
};
}
const links = buildExplorerLinks("YOUR_SIGNATURE", "devnet");
console.log("Official:", links.official);
console.log("Solscan: ", links.solscan);
console.log("SolanaFM:", links.solanaFm);Generating links for two or three explorers at once, instead of hardcoding just the official one, makes cross-verification a one-click habit for your team rather than something someone has to remember to do manually when a transaction looks wrong.
Common Beginner Mistakes
- Forgetting the cluster query param on devnet - the explorer defaults to mainnet-beta, so a devnet signature shows "not found." Fix: always append
?cluster=devnet(or the equivalent for the explorer you're using). - Trusting one explorer's summary as ground truth - indexers lag and occasionally mis-decode complex instructions. Fix: cross-check anything surprising on a second explorer or raw RPC, as shown in Step 4.
- Confusing "not found" with "failed" - a signature the explorer can't find yet may just not be indexed, while a failed transaction is indexed but shows an error. Fix: query RPC directly (
getSignatureStatuses) if the distinction matters to your code. - Using a general-purpose explorer to judge validator health - Solscan and the official Explorer aren't built for staking/APY/delinquency detail. Fix: use a validator-focused tool like Solana Beach for that data.
- Assuming every explorer indexes historical data equally far back - retention windows differ by provider and plan. Fix: check an explorer's documented history depth before relying on it for old transactions.
- Sharing a mainnet-beta explorer link when you meant devnet (or vice versa) - easy to do since the URLs differ by one query param. Fix: always double-check the cluster in the link before sending it to a teammate.
FAQs
Which explorer should I use as my default?
Solscan is the most common day-to-day default, similar to how Etherscan is used on Ethereum. The official Explorer is a good ground-truth fallback since the Solana Foundation runs it directly.
Why does a transaction show up on one explorer but not another?
Explorers run independent indexers with different processing speeds and, sometimes, different retention windows. A short delay or an older transaction can appear on one before (or instead of) another.
Do I need an API key to use these explorers?
Not for browsing the website. Several - Solscan and Orb among them - offer optional paid or free-tier APIs if you want to query their indexed data programmatically instead of using raw RPC.
What's the difference between an explorer and an RPC provider?
An RPC provider (see RPC Providers) is infrastructure your code talks to directly. An explorer is a website built on top of RPC data for humans to browse - you don't call an explorer from your application code.
Can I see NFT rarity and sales history on a general-purpose explorer?
Solscan and similar general-purpose explorers do show basic NFT metadata and history. For deep rarity traits and marketplace listings, a dedicated NFT marketplace or analytics tool is often more thorough.
What is TPS, and where do I see it?
Transactions Per Second - a network-level throughput metric. General-purpose explorers like SolanaFM surface it on their network stats dashboards.
Is Orb the same thing as Helius?
Orb is a block explorer product built by Helius, the RPC provider covered in RPC Providers. They're related products from the same company, not the same tool.
What does "delinquent" mean on a validator explorer?
It means a validator has stopped voting on the chain - a health signal for stakers and node operators, surfaced on tools like Solana Beach.
Should I trust an AI-generated transaction summary from an explorer?
Treat it as a helpful starting point, not a verified fact - AI summaries (like Orb's) are generated from the same decoded data you could read yourself, and can still misinterpret an unusual instruction.
Do explorers work for localnet?
No. Public explorers only index public clusters (mainnet-beta, devnet, testnet). For solana-test-validator, use CLI tools like solana confirm -v and solana logs instead, as covered in Wallets & Explorers.
What's a fast way to check MEV activity on a transaction?
Use a specialized tool like the Jito MEV Explorer, which is built specifically for bundle and searcher activity that general-purpose explorers don't surface in detail.
Related
- Wallets & Explorers - the devnet explorer workflow this page builds on
- Types of Wallets - the wallets whose activity you're inspecting in an explorer
- RPC Providers - the underlying data source every explorer indexes
- Clusters & Networks - matching an explorer's cluster param to where your transaction actually happened
Stack versions: This page was written for Agave 4.1.1, Solana CLI 3.0.10, and @solana/kit 7.0.0.