crosschain.evm Table: dim_contract_abis Type: View
What
This table contains Application Binary Interfaces (ABIs) for smart contracts deployed on EVM blockchains. ABIs define the contract’s functions, events, and data structures, enabling the decoding of raw blockchain data into human-readable format. It contains a column for the blockchain the contract is deployed on, which is an important filter and join key. See evm.dim_chains for a list of all supported EVM chains.Key Use Cases
- Decoding raw event logs into human-readable format
- Identifying contract functions and their parameters
- Enabling interaction with smart contracts programmatically
- Analyzing contract patterns and implementations across chains
- Supporting automated contract verification and bytecode matching
Important Relationships
- Powers evm__ez_decoded_event_logs: ABIs enable event decoding
- Join with evm__dim_contracts: Use
contract_addressandblockchainfor contract metadata - Enables fact_decoded_event_logs: Raw to decoded transformation
Commonly-used Fields
contract_address: The contract’s blockchain addressabi: The contract’s Application Binary Interface in JSON formatabi_source: The origin of the ABI data (explorer verified, user submitted, bytecode matched)bytecode: The compiled contract code deployed on-chaincreated_timestamp: When the ABI was added to the databaseblockchain: The blockchain the contract is deployed on
Sample queries
Find Contracts Without ABIsColumns
| Column Name | Data Type | Description |
|---|---|---|
| BLOCKCHAIN | TEXT | The blockchain the record occurred on. See evm.dim_chains for a list of all EVM chains. Format: VARCHAR Example: ‘ethereum’ Usage: Filtering by blockchain Joining across tables Analyzing chain-specific patterns |
| CONTRACT_ADDRESS | TEXT | Unique identifier - the deployed contract’s blockchain address. Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’ |
| ABI | VARIANT | The contract’s Application Binary Interface in JSON format, containing function and event definitions that enable interaction with the smart contract. Example: ‘[{"name":"transfer","type":"function","inputs":[{"name":"to","type":"address"},{"name":"value","type":"uint256"}],“outputs”:[{"name":"","type":"bool"}]}]‘ |
| ABI_SOURCE | TEXT | The origin of the ABI data, indicating trust level and collection method. Example: ‘etherscan’ |
| BYTECODE | TEXT | The compiled contract code deployed on-chain, used for bytecode matching and identifying identical contracts. Example: ‘0x608060405234801561001057600080fd5b50…’ |
| DIM_CONTRACT_ABIS_ID | TEXT | DIM_CONTRACT_ABIS_ID column |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | INSERTED_TIMESTAMP column |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | MODIFIED_TIMESTAMP column |