Searching
The search bar at the top of every page accepts multiple formats. Sonde detects the input type automatically and routes you to the right page.
Supported formats
| Input | Example | Goes to |
|---|---|---|
| r-address | rPEPPER7kf...c6GDY | Account page |
| X-address | X7AcgcsBL8...q3bJx | Account page (decoded) |
| Transaction hash | 3D64A3629DD0...F436F90 | Transaction detail |
| CTID | C42B19AB00290008 | Transaction detail |
| Address + DT | rAddress:12345 | Account (filtered by tag) |
| Address + DT | rAddress DT:42 | Account (filtered by tag) |
| NFT ID | 000800005A...1C3E | NFT detail |
| Ledger index | 69933483 | Ledger page |
| Currency code | USD | Token search |
| Currency hash | 0158415500...000000 | Token search |
| PayString | user$example.com | Resolved account |
CTID (Compact Transaction ID)
A CTID is a 16-character hex string that encodes a transaction's position in the ledger: the ledger index, transaction index within that ledger, and network ID. It's shorter and easier to share than a full 64-character hash. Sonde computes CTIDs automatically on every transaction detail page and supports searching by CTID.
Destination tag search
Exchanges use destination tags to identify individual users sharing a single XRP address. You can search rAddress:12345 or rAddress DT:12345 to jump directly to that account with the transactions tab filtered to only show transactions matching that tag.
How resolution works
For unambiguous inputs (addresses, ledger indices), Sonde routes instantly on the client. For 64-character hex strings — which could be a transaction hash, NFT ID, or ledger object — Sonde tries each possibility on the server: transaction cache, then NFT lookup, then transaction fetch, then ledger entry. The first match wins.