Search by name, SuiNS, address, digest, object ID, coin type or checkpoint.

API
History

Get started

History

tide keeps every transaction, event, balance change and object version since genesis. Ask about any date.

History is the same on every plan and every call. Time arguments take a unix time, an ISO datetime or a checkpoint. The answer says which checkpoint it used in asOf.

Balances and holdings

  • wallet.balanceAt returns one coin balance of an address at a time or checkpoint.
  • wallet.holdingsAt returns every coin balance of an address at a time or checkpoint, with USD at the price of that time.

Holders

Address history

  • getTransactionsForAddress pages through all of an address's history, newest or oldest first. Filter by checkpoint range, time range, status, type, coin, direction and role.
  • tx.history returns the same history as parsed transactions, paged with before and until.
  • wallet.history and wallet.transfers give the same history from the wallet side.

Objects

Events

  • events.list returns events of a type or package over a time or checkpoint range.

Replay

Streams and webhooks can replay from any checkpoint your plan allows, then join the live tail with no gap and no duplicate. Free replays 7 days, Developer 90 days, Business and above all the way back to genesis. See Streams and Webhooks.

What is not stored

tide stores versions, owners, types and coin balances. It does not store the contents of an object at a past version, for example a pool's reserves last month. Reading objects at a past version is planned.

If you ask for a range the index does not cover yet, you get not_indexed with the lowest checkpoint it can answer from.

QuestionAnswer
How far back?To genesis for balances, transfers, transactions, events and object versions.
How fresh?About a second behind the chain. See asOf.lagMs.
Same on the free plan?Yes. Only volume and speed differ.