Skip to main content
POST
https://api.blockdb.io
/
v1
/
evm
/
lineage
/
record
curl -X POST "https://api.blockdb.io/v1/evm/lineage/record" \
  -H "Authorization: Bearer $BLOCKDB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "chain_id": 1,
  "tracing_id": "0201000000000000000000000000000000000001"
}'

{
  "meta": {
    "chain_id": 1,
    "tracing_id": "0201000000000000000000000000000000000001"
  },
  "data": {
    "dataset": "blockdb_evm.b0201_erc20_tokens_v1",
    "record": {
      "chain_id": 1,
      "address": "0000000000000000000000000000000000000001",
      "name": "Token Name",
      "symbol": "TOKEN",
      "decimals": 18,
      "block_number": 567890,
      "block_time": "2018-07-07T12:34:56Z",
      "tx_index": 4,
      "log_index": 2,
      "_tracing_id": "0201000000000000000000000000000000000001",
      "_parent_tracing_ids": [
        "0103000000000000000000000000000000000001",
        "0103000000000000000000000000000000000002"
      ],
      "_created_at": "2025-11-11T18:42:15.123Z",
      "_updated_at": "2025-11-11T18:42:15.123Z"
    }
  }
}

​
Description

Retrieves the canonical BlockDB representation of a single record, keyed by its lineage identifier. This is the lightweight entry point before requesting heavier genesis or parent expansions.

​
Parameters

​
chain_id
number
required
EVM network identifier. See the Chain enumeration for supported values.
​
tracing_id
string
required
Lineage identifier for the target record (hex string, no 0x prefix). The legacy _tracing_id key is still accepted.

​
Response Fields

​
Meta

​
meta
object
Echo of request metadata applied to the response.
​
meta.chain_id
number
EVM chain ID echoed from the request.
​
meta.tracing_id
string
Tracing identifier for the record whose artifacts are returned.

​
Data

​
data
object
Envelope containing the record payload.
​
data.dataset
string
Dataset namespace that owns the record (e.g., 0201_tokens-erc20).
​
data.record
object
Snapshot of the dataset-specific fields for this record. Common metadata includes:
​
data.record.chain_id
number
Network identifier copied from the envelope.
​
data.record.address
string
Dataset-specific primary key (illustrated here with a token contract address).
​
data.record.block_number
number
Canonical block height where the record last changed.
​
data.record.block_time
string
ISO-8601 timestamp for the block that produced the record state.
​
data.record.tx_index
number
Transaction position for provenance auditing when applicable.
​
data.record.log_index
number
Log position for provenance auditing when applicable.
​
data.record._tracing_id
string
Internal variant of tracing_id.
​
data.record._parent_tracing_ids
string[]
Internal variant mirrored for completeness.
​
data.record._created_at
string
Internal created-at timestamp.
​
data.record._updated_at
string
Internal updated-at timestamp.
  • name, symbol, decimals
    Dataset fields shown for the ERC-20 example. Actual shape varies per dataset—consult the dataset’s schema docs.

​
Next Steps

curl -X POST "https://api.blockdb.io/v1/evm/lineage/record" \
  -H "Authorization: Bearer $BLOCKDB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "chain_id": 1,
  "tracing_id": "0201000000000000000000000000000000000001"
}'

{
  "meta": {
    "chain_id": 1,
    "tracing_id": "0201000000000000000000000000000000000001"
  },
  "data": {
    "dataset": "blockdb_evm.b0201_erc20_tokens_v1",
    "record": {
      "chain_id": 1,
      "address": "0000000000000000000000000000000000000001",
      "name": "Token Name",
      "symbol": "TOKEN",
      "decimals": 18,
      "block_number": 567890,
      "block_time": "2018-07-07T12:34:56Z",
      "tx_index": 4,
      "log_index": 2,
      "_tracing_id": "0201000000000000000000000000000000000001",
      "_parent_tracing_ids": [
        "0103000000000000000000000000000000000001",
        "0103000000000000000000000000000000000002"
      ],
      "_created_at": "2025-11-11T18:42:15.123Z",
      "_updated_at": "2025-11-11T18:42:15.123Z"
    }
  }
}