Skip to main content
A blockchain indexer continuously reads a chain’s ledgers, decodes them, and turns them into structured, queryable data. Mobula’s Stellar indexer converts XDR-encoded ledgers and Soroban contract events into normalized tokens, trades, prices, liquidity, transfers, and wallet balances — served over the same REST API and WebSocket streams as every other chain, so you never run a Stellar node or decode XDR yourself. This page covers what’s available, how ledgers are indexed, and the semantics you’ll need to consume the data.

​
Environments & identifiers

Both mainnet and testnet run in production. Address formats you’ll pass to the API:
  • Account — G… (e.g. GDHF3HIKWM5KJAVLZBSZWUFDOEOT7IBMY22UXG4QBE326O354INLPAND)
  • Asset — CODE:ISSUER (e.g. AQUA:GBNZILSTVQZ4R7IKQDGHYGY2QXL5QOFJYQMXPKWRRM5PAV7Y4M67AQUA)
  • Contract / market — C… (e.g. CBRUQ7I6C6OGHMDYWD6XQUZFB6KJ3LLPNE34EPKSPFZ2YMBJ2GIWYYZ7)
  • Native XLM is addressable as the sentinel 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee.

​
What’s available

Not covered on Stellar: swap quote/execution routing (read-only DEX data only) and NFT holdings.

​
Indexing

A dedicated Stellar listener ingests every ledger as it closes. One ledger maps 1:1 to a block and is processed in order — there’s no shard or slot reconciliation — so trades, transfers, and pool state are decoded and served within about one ledger of the network. Stellar also differs from most chains in how its data is exposed: rather than a single archive node serving everything, its RPC retains only a short window of recent ledgers. Mobula reads from both source types:
  • Real-time — new ledgers are read from Stellar RPC as they close.
  • Historical — because RPC retention is short, earlier ledgers are backfilled from Horizon and other archival providers.
Latency (production, mainnet): head lag p50 ≈ 5.3 s, p95 ≈ 7.0 s — roughly one Stellar ledger period (~5.6 s), i.e. the listener sits at live tip. Every ledger is indexed in sequence — no sampling, no gaps — and because Stellar ledgers are final on close (no reorgs), indexed data is never reverted.

​
Working with Stellar data

A few Stellar-specific semantics to know before you consume the API:

​
Your first call

Fetch metadata for a Stellar asset — nothing to set up beyond the request: Using cURL:
An API key from the Dashboard is required for production use (the API is usable without a key in development).

​
Next steps

  • How to Use Stellar Data — a tutorial covering historical transaction lookups, token liquidity insights, contract interaction data, and real-time streams.
  • Stellar API Reference — full endpoint list, chain identifiers and address formats.

​
Need Help?

Our support team is available to assist with your queries or integration issues.

Support

Telegram

Support

Slack

Support

Discord

Email Support

Email