Skip to main content
Schema: ethereum.nft Table: dim_nft_collection_metadata Type: View This table contains the metadata for popular NFT collections on the Ethereum blockchain.

ā€‹
Columns

Column NameData TypeDescription
BLOCKCHAINTEXTBlockchain where the NFT metadata is retrieved from.
CONTRACT_ADDRESSTEXTThe 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(block_number, tx_hash, 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: 
-- Check data latency
SELECT
    DATE_TRUNC('hour', block_timestamp) as block_hour,
    DATE_TRUNC('hour', inserted_timestamp) as insert_hour,
    AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes
FROM <blockchain_name>.core.fact_transactions
WHERE block_timestamp >= CURRENT_DATE - 1
GROUP BY 1, 2;
``` |
| 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**:
```sql
-- Recently modified records
SELECT *
FROM <blockchain_name>.core.fact_transactions
WHERE modified_timestamp > inserted_timestamp
AND modified_timestamp >= CURRENT_DATE - 1;

-- Data quality tracking
SELECT
    DATE(modified_timestamp) as mod_date,
    COUNT(*) as records_updated,
    COUNT(DISTINCT block_number) as blocks_affected
FROM <blockchain_name>.core.fact_transactions
WHERE modified_timestamp > inserted_timestamp
GROUP BY 1
ORDER BY 1 DESC;
``` |