Skip to main content
POST

Overview

  • Dataset ID: 0121 - Contracts
  • Description: Smart contracts discovered via CREATE/CREATE2 internal transactions. Uses contract_id (26 bytes = address + creation_block + tx_index) as primary key to support metamorphic contracts (e.g. CREATE-SELFDESTRUCT-CREATE2 in the same block).
  • CSV Sample: Download
  • JSON Sample: Download

Parameters

number
required
Target EVM network. See the Chain enumeration for supported values.

Range Filters (mutually exclusive with direct selectors)

number
Starting block number (inclusive) for the query. Use with to_block.
number
Ending block number (inclusive) for the query. Use with from_block.
string
Starting timestamp (ISO-8601). If it falls between blocks, the next block after this timestamp is used. Use with to_timestamp.
string
Ending timestamp (ISO-8601). If it falls between blocks, the last block before this timestamp is used. Use with from_timestamp.
Scoping rule: Provide exactly one of:
  1. Block range — from_block and to_block
  2. Time range — from_timestamp and to_timestamp
  3. Direct selectors — presented below
Direct selectors may be used on their own, without a block or time range. Do not combine scoping modes. Omitting all three returns HTTP 400.

Direct Selectors

string[]
Filter by specific deployed contract addresses (hex string, 20 bytes, no 0x prefix). Up to 256 addresses per request.
number[]
Explicit list of block heights to fetch contract deployments from. Mutually exclusive with the range filters.

Pagination Controls

number
default:"250"
Recommended default 250; maximum 1000 to stay under ~10 MB responses.
string
Opaque pagination cursor supplied by a previous response.

Response Fields

Meta

object
Echo of request metadata applied to the response.
number
EVM chain ID echoed from the request.
object
Pure echo of the window you sent (from_block/to_block/from_timestamp/to_timestamp); unset bounds are null.
object | null
The concrete window the query actually executed against, after resolving the request. For a block range on a time-bucketed endpoint (OHLC/VWAP/VWAP-aggregate/fiat VWAP), from_timestamp/to_timestamp hold the resolved timestamp window (and from_block/to_block echo your request). For a time range on a block-keyed endpoint, from_block/to_block hold the resolved block range (and the timestamps echo your request). null for selector-only requests (no window). No extra database work is done — these are the values the query already computed.
number | null
Resolved/echoed start block of the executed window.
number | null
Resolved/echoed end block of the executed window.
string | null
Resolved/echoed start timestamp (ISO-8601) of the executed window.
string | null
Resolved/echoed end timestamp (ISO-8601) of the executed window.
object
Filters echoed from the request (contract addresses, block numbers, limit).

Data

object[]
Each element mirrors the table columns (chain implied by meta.chain_id).
string
Unique contract incarnation ID (hex string, 26 bytes, no 0x prefix): 20 bytes address + 4 bytes creation block + 2 bytes tx_index. Use for metamorphic disambiguation and to join with function-results.
string
Deployed contract address (hex string, 20 bytes, no 0x prefix). Use for address-based lookups.
number
Block height containing the contract creation.
string
ISO-8601 UTC timestamp of the creation block, joined from the blocks dataset.
number
Zero-based index of the deployment transaction within the block.
string
Position in the call tree (e.g., "0", "0.0", "0.1.2").
string
Address that deployed the contract (msg.sender of CREATE/CREATE2). Hex string, 20 bytes, no 0x prefix.
string
Type of creation: CREATE or CREATE2.
string
Internal tracing identifier for lineage tracking (hex string, no 0x prefix).
string
Timestamp when BlockDB materialized the record.
string
Timestamp of the latest update to the record.

Envelope Fields

string | null
Pagination cursor to continue the query.
number
Number of records in the current page.

Use Cases

  • Look up the canonical creation block for a contract address before hydrating additional metadata.
  • Backfill on-chain analyses that require the deployment timestamp or transaction location.
  • Seed lineage exploration using _tracing_id to pivot into /evm/logs and /evm/transactions.
Last modified on July 19, 2026