Skip to main content
All v1.2.0 datasets (transactions, operations, events, ledgers, ledger_entries, transfers) support starting from a specific ledger sequence using start_at: <ledger_sequence> (e.g., start_at: 60000000). This significantly reduces backfill times compared to starting from earliest.
v1.2.0 performance improvements: Single-pass Arrow builders and optimized memory usage provide faster processing and lower resource consumption.

Dataset configuration

For resource sizing options, see Pipeline Configuration.
When using end_at, combine with job: true at the top level so the pipeline auto-terminates after completion. See Job Mode for details.
Be cautious when increasing fetch_batch_size in job mode. Jobs do not automatically restart on failure, so resource errors (e.g., out of memory) will cause the job to fail permanently.

Quick start

The fastest way to explore Stellar data is using a blackhole sink with goldsky turbo inspect:
For testnet, simply swap the stellar_mainnet prefix with stellar_testnet in the dataset_name:

Guide: Monitor transfers for specific assets

For more sink types and configuration options, see turbo sinks docs.

Guide: Track transactions of a specific account

Guide: Track contract activity

Guide: Monitor account balances


Dataset schemas

Full field reference for all Stellar datasets.

Deprecated versions

The following dataset versions are no longer supported and should be migrated to the current stellar_mainnet.* datasets.
These datasets were used with the Mirror product and are no longer supported.
For any questions or feedback, reach out at support@goldsky.com.