Registry

One row per contract’s first deployment: one address on one chain, with the accounts behind its creation and the size of the code it deployed. It holds every contract we see onchain, far past the ones anyone has labeled, and Accounts holds those labels.

Columns

Column	Type	Description
`contract_id`	`INT64`	Fingerprint of `account_id`, stable across runs.
`account_id`	`STRING`	Contract as an account: `{contract_address}-{chain_id}`. The same pair as one key, for joining `dimensions.accounts` and `dimensions.tokens`.
`chain_id`	`STRING`	Chain the contract is deployed on. With `contract_address` it is the cluster key and the pair to filter on: the same address on two chains is two different contracts.
`contract_address`	`STRING`	Address of the contract, spelled the way its chain spells it: lowercase on EVM and Starknet, base58 and case-sensitive on Solana and Tron. Lowercase an EVM address copied from an explorer before matching it here.
`first_deployed_at`	`TIMESTAMP`	Time the address first held code. An address can be created, destroyed with `SELFDESTRUCT` and created again; the row describes that first creation.
`deployer_address`	`STRING`	Account that signed the first deployment’s transaction.
`creator_address`	`STRING`	Account that called `CREATE` on the first deployment. Equals `deployer_address` for a direct creation, and differs where a factory contract creates on the signer’s behalf.
`contract_size`	`FLOAT64`	Deployed bytecode size in bytes, on the first deployment.

Sample queries

The table is clustered on chain_id and contract_address, and every row is current rather than dated. Filter on the chain, and on the address where you have it; a query that filters on neither reads the whole table.

Look up a contract
What one account deployed
Name a contract

Filter chain_id and contract_address together, since that pair is the cluster key. Lowercase an EVM address copied from an explorer before you paste it in.

select
    first_deployed_at,
    deployer_address,
    creator_address,
    contract_size
from `dimensions.contracts`
where chain_id = 'ethereum'
  and contract_address = '0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2'

creator_address is the account that called CREATE, so filtering it returns a factory’s output; filter deployer_address instead for the contracts an account signed for.

select
    contract_address,
    first_deployed_at,
    contract_size
from `dimensions.contracts`
where chain_id = 'ethereum'
  and creator_address = '0x1f98431c8ad98523631ae4a59f267346ea31f984'
order by first_deployed_at
limit 100

dimensions.accounts holds the label, and the two tables join on account_id. An inner join keeps the contracts somebody has attributed, so the project filter reads against a labelled set.

select
    contracts.contract_address,
    contracts.first_deployed_at,
    accounts.project_id,
    accounts.contract_name
from `dimensions.contracts` as contracts
join `dimensions.accounts` as accounts
    using (account_id)
where contracts.chain_id = 'ethereum'
  and accounts.project_id = 'uniswap'
order by contracts.first_deployed_at
limit 100

Overview

Popular datasets

Market verticals

Chain ecosystems

Core entities

Columns

Sample queries

​Columns

​Sample queries

Columns

Sample queries