Find a contract deployment
portal_evm_get_contract_deploymentLocate the create trace and parent transaction that deployed a specific EVM contract address within a bounded window.
COMMON USER ASKS:
Find BAYC deployment
Find recent deployment
Find deployment from known range
FIRST CHOICE FOR:
who deployed this EVM contract
when was this contract deployed
what deployment transaction created this contract
WHEN TO USE:
You need the deployer, deployment block, deployment timestamp, or deployment transaction for an EVM contract.
You can provide a starting block/time window, a contract address, or a supported well-known contract alias such as BAYC/Bored Apes.
You want a deployment lookup instead of general contract activity.
DON'T USE:
You need all activity for a contract after deployment.
The contract is old and no block/time hint is available; provide from_block or from_timestamp first.
EXAMPLES:
Find BAYC deployment: {"network":"ethereum-mainnet","contract":"bored apes","from_block":12000000,"to_block":13000000,"scan_order":"earliest"}
Find recent deployment: {"network":"base-mainnet","contract_address":"0xabc...","search_depth_blocks":100000}
Find deployment from known range: {"network":"ethereum-mainnet","contract_address":"0xabc...","from_block":17000000,"to_block":17100000,"scan_order":"earliest"}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| network | Yes | EVM network name or alias, e.g. base, ethereum, arbitrum. | |
| contract | No | Contract address or a supported well-known alias/name, e.g. "bayc" or "bored apes" on Ethereum. | |
| to_block | No | Optional ending block. Defaults to the indexed head. | |
| timeframe | No | Optional recent time window to search, e.g. "24h" or "7d". | |
| from_block | No | Optional starting block. Provide this for older contracts when the deployment is not recent. | |
| scan_order | No | Scan latest first for recent deployments, or earliest first when you provide a historical from_block. | latest |
| to_timestamp | No | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| from_timestamp | No | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "7d ago". | |
| max_scan_blocks | No | Safety cap for historical deployment scans. Default: scan the requested window up to 1,000,000 blocks. | |
| contract_address | No | Contract address whose deployment transaction should be located. | |
| search_depth_blocks | No | When no explicit range is given, search this many recent blocks backward from the indexed head. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| _ui | No | Chart, table, and follow-up presentation metadata. | |
| _app | No | SQD Explorer identity and host-render state. | |
| _llm | No | Hints to locate the primary evidence. | |
| _meta | No | Network, block range, timing, and row counts. | |
| error | No | Structured failure details. | |
| items | No | Primary rows for list results. | |
| value | No | Primary scalar result. | |
| answer | No | Answer grounded in the returned data. | |
| _notice | No | Limitation or truncation notice. | |
| _server | No | SQD server name, exact version, and git commit. | |
| display | No | Labels for presenting the result. | |
| _notices | No | Limitation or truncation notices. | |
| _summary | No | Human-readable summary. | |
| _coverage | No | Window and result completeness. | |
| _evidence | No | Replayable arguments, digest, row count, and receipt. | |
| _ordering | No | Ordering guarantees. | |
| _execution | No | Bounded execution and scan details. | |
| _freshness | No | Freshness and finality. | |
| next_steps | No | Safe follow-up actions and continuation guidance. | |
| _pagination | No | Pagination state and next_cursor. | |
| investigation | No | Evidence paths, pivots, and limitations. | |
| pipes_handoff | No | SQD Pipes guidance for custom data needs. | |
| _tool_contract | No | Tool identity, intent, and chain families. |