Crypto tools that cover Solana

What a Solana claim is worth differs more than on any other chain — and on a few cards it means a payment rail rather than coverage.

Last updated

The word is the same on every card, the claim is not

Every card on this page names Solana in its coverage. Eleven are on-chain analytics platforms, eight are market-data APIs, four are charting platforms and one is a bot framework. Eighteen have a free tier and seventeen carry at least one tier with no published number, which puts this shelf at roughly the catalogue's own average on both counts.

What is not average is how far apart the claims are. On Ethereum, "supported" means much the same thing from one vendor to the next: they are all decoding the same logs with the same machinery. On Solana it ranges from a full decoded stack to eight hours of raw retention.

Why this chain, and not a page per chain

Every other chain in the catalogue would clear the bar to have a page like this one — ethereum at 35 cards, arbitrum 26, polygon 25, base and BNB 23, bitcoin 19 — and none of them will get one. Solana is here because it is the only chain in the list that is not EVM, and that is a fact about the work rather than about the marketing.

An EVM chain emits logs. A vendor writes one decoder, points it at an ABI, and then points the same pipeline at forty chains — which is exactly what the "40+ chains" headlines on this page are describing. Solana has no logs to decode. It has instructions, inner instructions, account writes and vote transactions that have to be separated out before anything else makes sense, and an IDL in place of an ABI. Every vendor here built a second pipeline for it, and the cards record which ones finished.

Dune is the finished end: Solana has its own table shape — instruction_calls, account_activity, vote-transaction separation, IDL decoding submissions, dex_solana.trades and Jupiter aggregator swaps — rather than being squeezed into the EVM schema. Allium does the same thing with raw instructions, inner instructions, non-voting variants of each and SPL token tables.

Bitquery is the other end, and it is explicit about it: events and calls do not exist on Solana at all, and balances on the Solana archive pack are reconstructed from transfer history rather than served directly. The same card's self-service tier keeps four hours of raw EVM data and eight hours of Solana — and the Solana archive pack is its most expensive per-chain add-on, at 300 and 500 dollars a month for the two halves.

Where the free path stops

Not at the chain. It stops at history.

Kaiko covers Bitcoin, Ethereum and Solana back to genesis, with one exception written into the standard package: Solana ships 30 days of rolling history, and inception-to-date is a custom deal. Coin Metrics has Solana's series and gates them — the active-address series exists, it is simply not on the tier you can buy with a card. Amberdata supports four chains fully and marks Solana as available with select endpoints while backfills and verification are ongoing. Nansen starts its Solana history on 17 March 2020, which is a real date and a short one next to its Ethereum series from 2015.

So the order to read a card in is: chain list, then retention, then tier. The first is marketing, the second is the product, and the third is the invoice.

The thing that is not a dataset

Three cards here — Nansen, Arkham and Messari — accept x402 micropayments settled in USDC on Base or on Solana, with no account and no API key. That is Solana appearing on a card as a payment rail, and the coverage field next to it is a different claim about a different thing.

The Laevitas API does the same and is not on this page, because it indexes no chain at all — which is the distinction working. Taking Solana money and reading Solana are two things, and only the second is a coverage claim.

The larger version of the same confusion is the one worth naming. A Solana RPC endpoint is not a data product. It will answer for an account, a signature or a block, which is what it is built for. It will not tell you what a pool traded, who holds a token, or how a protocol's fees moved last quarter, because those are not questions about accounts — they are questions about programs, and answering them means decoding every program's instructions and maintaining that decoding through every redeployment. That work is the entire product on this page. Node providers and indexing backends are not in this catalogue at all, for the reason the on-chain analytics page gives: an RPC endpoint is plumbing.

Only one card here is open source — Hummingbot, which ships a Solana connector and DEX connectors for Jupiter, Meteora, Orca, Raydium and Titan. It is on this page because it trades there, not because it indexes anything.

What is not here

Several products a Solana reader would expect. CryptoQuant classifies Solana as an altcoin symbol carrying exchange price data with no on-chain metrics behind it. Santiment lists Solana on two vendor pages and its live API did not return it. Trading Strategy is EVM-only and says so. growthepie and L2BEAT are Ethereum layer-two projects by design. None of them is on this page, and none of that is an accident of wording: the coverage field says what the card checked.

All 24 of them

Showing 24 of 24

FAQ

Is an RPC endpoint enough to get Solana data?

For one account or one transaction, yes. For anything with a shape — DEX volume, holders over time, a protocol's fees — no, and this is the mistake that costs the most time. A Solana RPC node answers questions about accounts and signatures; it does not answer questions about markets. Turning one into the other means decoding every program's instructions yourself and keeping up when a program is redeployed. That decoding is the product every card on this page is selling, and no node provider does it for you.

Why is Solana coverage thinner than Ethereum coverage almost everywhere?

Because Solana is not EVM and the indexing work does not transfer. An EVM chain emits logs that an ABI decodes, which is why a vendor can point the same machinery at forty chains at once. Solana has instructions, inner instructions and account writes instead, and an IDL rather than an ABI. Every vendor here has had to build a second pipeline for it, and the cards show which ones finished.

Does "supports Solana" mean full history?

Not by default, and the difference is usually in a sentence nobody reads. Kaiko's standard package ships a rolling 30 days of Solana and sells inception-to-date as a custom deal. Bitquery's self-service tier keeps eight hours of raw Solana data and sells the archive separately. Coin Metrics has the series and gates them. Read the retention line before the chain list.

Why does Solana show up on cards that have nothing to do with Solana data?

Because it is being used to take payment. Three cards here accept x402 micropayments — an HTTP 402 challenge you settle in USDC, on Base or on Solana, with no account and no API key. That is Solana as a settlement rail, not as a dataset, and the coverage field on those cards is claiming the data. Read the pricing section to find out which one a card means.