XRP goes live: 12 chains for self-serve scanning, full XRPL history included

On 2026-08-09, XRP (XRP Ledger) became a fully supported chain on ChainAnalyzer. Beyond native XRP payments, we now scan IOU (issued-currency) tokens too, with the same feature set as every other chain: one-off scans, Watchlist monitoring, Follow Mode graph exploration, and Case Management. That brings self-serve live chains to 12: Bitcoin, Ethereum, Polygon, BNB Smart Chain, Base, Arbitrum, Optimism, Avalanche, Solana, Kaia, TRON, and XRP.

Live on every plan, including Free, from day one

XRP is available on every plan, including Free, starting today. Sign up and scan an XRP address immediately — Starter and above get batch scanning, Watchlist monitoring, REST API, and x402 support for XRP as well.

Full history, no API key required

The XRP Ledger runs on Ripple's official full-history clusters (s2.ripple.com, with xrplcluster.com as fallback) — public infrastructure that needs no credential at all. Unlike EVM chains that require an Etherscan-family API key, or TRON where we integrate a dedicated API provider, there's no BYOK setting for XRP: every user gets the same full-history access on day one.

Partial Payment correction: the amount actually received, not the amount advertised

XRPL supports Partial Payment, a transaction type where the sender can settle for less than the amount originally specified — meaning the headline transfer amount in raw transaction data can overstate what actually moved. ChainAnalyzer corrects every Partial-Payment-flagged transaction against the delivered_amount field, so fund-flow analysis and risk scoring are always based on the amount actually delivered, not the advertised send amount.

Same detection depth as every other chain, plus a Destination Tag disclosure

OFAC sanctions screening, sanctioned-counterparty detection, dust attack detection, peel chain and fund-splitting detection, and KYT risk rating all run on XRP exactly as they do elsewhere. ScamDB matching, Follow Mode graph exploration, and case ingestion work unchanged.

One XRPL-specific nuance we surface directly in the scan result: exchanges commonly share a single deposit address across many users and tell customers apart with a Destination Tag. A scan verdict on such an address can therefore reflect the activity of the exchange as a whole rather than one individual user — tag-level analysis is not supported, and we disclose this explicitly wherever it applies.