Search and ledger history

Choose what to find#

Search from Explore or the header search icon. Enter an XRPL address, transaction hash, ledger number, token name, NFT or collection name, or an XRPFrontend @username. Results are grouped by type. Addresses open account details. Transactions open their ledger evidence. Tokens and collections open their existing market pages. Name indexing is Mainnet-only; public usernames remain Mainnet directory records even when Testnet is selected.

Use tx: followed by a transaction hash, nft: followed by an NFTokenID, check: or escrow: followed by a ledger object ID, or ledger: followed by a ledger number to narrow a search. An unprefixed 64-character hexadecimal ID is checked as a transaction, then a current ledger object, then an NFT. Provider errors are shown separately from missing records.

Validated records and older activity#

Read-only transaction, ledger, object, NFT and public account-history requests use XRPL public nodes. A record is presented as validated only when the provider explicitly reports validation. Account activity loads 20 records at a time. Load older activity follows a cursor anchored to the first page’s maximum ledger. Type and UTC date filters apply only to the loaded records; load more to inspect older matches. The latest account balances and signing continue through the existing wallet connection.

Current ledger objects disappear after they are consumed or deleted. A cashed Check or finished escrow may therefore have no current object result; inspect its creation, cashing or finishing transaction, or the account’s activity. Full history means the provider’s retained ledger range, not a promise of records preceding that range.

Token search coverage#

Markets, the chart market selector, swap asset selectors and batch asset discovery use one server-side indexed search for names, tickers and issuer addresses. Search removes an optional leading dollar sign and tries a compact spelling when a spaced name has no exact match. Exact tickers are ranked ahead of incidental text matches. Token searches span categories, so a missing Memes tag does not hide a search result. Browsing without a query still uses the selected category and normal pagination.

Indexed search is bounded to 100 returned token matches per query and does not guarantee every token on the ledger is indexed. Result pages share a short in-memory cache. The market API key remains private on the server. Missing credentials and provider pauses are reported, never replaced with fabricated matches. Exact issuer and currency entry remains available in the chart selector and custom batch asset fields.

Sources, limits and privacy#

Public XRPL nodes have limited shared capacity and retained history that varies by operator. XRPFrontend applies a shared server-side request budget, a short burst ceiling, caching and per-client limits. It honors provider Retry-After pauses, does not automatically retry, and does not rotate endpoints to evade a rate limit. A busy provider can temporarily pause search. Sustained production traffic may require private capacity arranged with the provider.

Token, NFT and collection names use the documented XRPL.to API with the configured server-side market connection. Index metadata can be incomplete or misleading and is not an endorsement. Always inspect the exact issuer before trading. Without that connection, public profile and ledger searches still work and the missing index is disclosed. Public workspace search uses the existing discovery settings; private workspace settings and wallet listings are never returned by this search.

Search sends the submitted record identifier or name to the relevant data provider. No wallet seed, signing key, wallet session cookie or private workspace data is sent to these providers. Search does not sign or submit transactions.