ethereum.nft Table: dim_nft_collection_metadata Type: View
What
This table contains the metadata for popular NFT collections on the Ethereum blockchain.Columns
| Column Name | Data Type | Description |
|---|---|---|
| BLOCKCHAIN | TEXT | Blockchain where the NFT metadata is retrieved from. |
| CONTRACT_ADDRESS | TEXT | The smart contract address of the NFT collection. Supports ERC-721, ERC-1155, and custom implementations. Example: ‘0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d’ |
| COLLECTION_NAME | TEXT | The name for this NFT collection. |
| TOKEN_ID | TEXT | The unique identifier of the specific NFT within its collection. Format is numeric string. Example: ‘1234’ |
| TRAITS | VARIANT | The traits for this tokenId in a key-value pair format. |
| TOKEN_ID_NAME | TEXT | The name for this specific tokenId. This may be the same for all tokenIds within the same collection. |
| TOKEN_ID_DESCRIPTION | TEXT | The description for this specific tokenId. This may be the same for all tokenIds within the same collection. |
| TOKEN_ID_IMAGE_URL | TEXT | The url of the image for this tokenId. |
| NFT_ADDRESS_TOKEN_ID | TEXT | The concatenation of nft address and tokenId. |
| DIM_NFT_COLLECTION_METADATA_ID | TEXT | Primary key - unique identifier for each row ensuring data integrity. Format: Usually VARCHAR containing composite key generated using MD5 hash of the relevant columns. Example: MD5(blocknumber, txhash, trace_index) Usage: Deduplication in incremental loads Join operations for data quality checks Troubleshooting specific records Important: Implementation varies by table - check table-specific documentation. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the record was first added to the Flipside database. Format: TIMESTAMP_NTZ Use Cases: Data freshness monitoring Incremental processing markers Debugging data pipeline issues SLA tracking Query Example: |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp of the most recent update to this record. Format: TIMESTAMP_NTZ Triggers for Updates: Data corrections Enrichment additions Reprocessing for accuracy Schema migrations Monitoring Usage: |