Skip to main content

​
Description

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

EndpointSummaryDefault LimitTypical Latency
POST /evm/lineage/recordFetch the latest copy of a record by tracing identifier.1< 200 ms
POST /evm/lineage/genesisReturn the execution artifacts that seeded a record.256 artifacts~500 ms
POST /evm/lineage/parentsTraverse the dependency graph of parent records.128 nodesup to 1 s

​
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.
  • 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 and genesis artifacts are immutable once written.
  • Monitor truncation_reason (when present) to detect when depth or fan-out limits stop traversal.

​
See Also