Search across all documentation pages
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.
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.
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.
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.
| 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. |
Comprehensive tools for transactions, accounts, tokens, NFTs, programs, and basic analytics. Most user-friendly for everyday lookups.
Top popular ones:
Focus on deeper insights like MEV, validator performance, inner instructions, or developer debugging.
Top popular ones:
Primarily for node operators, staking, and ecosystem health metrics - fewer broad consumer options here than in the other two categories.
Main options:
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.
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.
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 .signatureEvery 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"));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"));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);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.
// 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.
?cluster=devnet (or the equivalent for the explorer you're using).getSignatureStatuses) if the distinction matters to your code.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.
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.
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.
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.
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.
Transactions Per Second - a network-level throughput metric. General-purpose explorers like SolanaFM surface it on their network stats dashboards.
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.
It means a validator has stopped voting on the chain - a health signal for stakers and node operators, surfaced on tools like Solana Beach.
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.
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.
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.
Stack versions: This page was written for Agave 4.1.1, Solana CLI 3.0.10, and @solana/kit 7.0.0.
Reviewed by Chris St. John·Last updated Jul 19, 2026