Description
Traverses the upstream dependency graph of the supplied record. Each node includes relationship metadata so you can follow the chain of derivations to a configurable depth.
Parameters
Anchor record whose parents should be returned, provided as a hex string (no 0x prefix).
Traversal Controls
Number of hops to follow. 1 returns direct parents, 2 includes grandparents, etc. Requests exceeding the configured maximum are truncated with a truncation_reason.
Recommended default 250; maximum 1000 to stay under ~10 MB responses.
Opaque pagination cursor returned from a prior call.
Response Fields
Echo of request metadata applied to the response.
EVM chain ID echoed from the request.
Tracing identifier for the record whose parents are returned.
Data
Each element represents a parent node that matches the requested depth and relationship filters.
Dataset namespace for the parent record.
Lineage identifier for the parent record (hex string, no 0x prefix). Feed this back into other lineage endpoints to continue traversal.
Hop count from the original record (1 for direct parents).
Envelope Fields
Pagination cursor for fetching additional parents.
Number of parent nodes returned in data.
Non-null when the server stopped traversal due to max depth, fan-out limits, or other safety guards.
Next Steps
curl -X POST "https://api.blockdb.io/v1/evm/lineage/parents" \
-H "Authorization: Bearer $BLOCKDB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"chain_id": 1,
"tracing_id": "0301000000000000000000000000000000000001",
"max_depth": 3,
"cursor": null,
"limit": 128
}'
{
"meta": {
"chain_id": 1,
"tracing_id": "0301000000000000000000000000000000000001"
},
"data": [
{
"dataset": "blockdb_evm.b0102_transactions_v1",
"_tracing_id": "0102000000000000000000000000000000000001",
"depth": 1
},
{
"dataset": "blockdb_evm.b0203_erc1155_tokens_v1",
"_tracing_id": "0203000000000000000000000000000000000002",
"depth": 1
}
],
"cursor": "next_cursor",
"count": 2,
"truncation_reason": null
}