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
number
required
Chain identifier to disambiguate networks. Refer to the Chain enumeration for supported values.
string
required
Selector for lineage requests (18-byte hex, exactly 36 characters, no
0x prefix). Matches values emitted in _tracing_id fields.string
Pagination cursor returned from prior responses; persist per endpoint when traversing large graphs.
number
Maximum number of records to return per page; lower values help manage payload size on expansive graphs.
Usage Guidance
- Start with
/evm/lineage/recordto confirm that atracing_idexists before requesting heavier expansions. A missing record comes back as200 OKwith"data": null, so checkdatarather than the status code. - Apply conservative
limitsettings 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.