Skip to main content

​
Overview

The lineage suite lets you reconstruct how a BlockDB record was produced. Each endpoint focuses on a specific slice of the lineage graph so you can tune limits, caching, and latency budgets independently.

​
Endpoint Matrix

​
Parameter Conventions

​
chain_id
number
required
Chain identifier to disambiguate networks. Refer to the Chain enumeration for supported values.
​
tracing_id
string
required
Selector for lineage requests (hex string (no 0x prefix)). Matches values emitted in _tracing_id fields.
​
cursor
string
Pagination cursor returned from prior responses; persist per endpoint when traversing large graphs.
​
limit
number
Maximum number of records to return per page; lower values help manage payload size on expansive graphs.

​
Usage Guidance

  • Start with /evm/lineage/record to confirm that a tracing_id exists before requesting heavier expansions. A missing record comes back as 200 OK with "data": null, so check data rather than the status code.
  • Apply conservative limit settings when exploring new datasets; payload size grows with artifact volume and graph breadth.
  • Cache lineage responses client-side where possible—records are immutable once written.
  • Monitor truncation_reason (when present) to detect when depth or fan-out limits stop traversal.

​
See Also

Last modified on July 2, 2026