| HOUR | TIMESTAMP_NTZ | The timestamp representing the hour when the price data was recorded or aggregated. Data type: TIMESTAMP. This field provides the temporal reference for hourly price data and is used for time-series analysis, price trend calculations, and temporal data aggregation. Used for hourly price tracking, time-based filtering, and chronological analysis of price movements. Example: ‘2024-01-15 14:00:00’ for the hour starting at 2 PM on January 15, 2024. Critical for time-series analytics, price volatility calculations, and maintaining temporal consistency in financial data analysis. |
| TOKEN_ADDRESS | TEXT | The blockchain-specific contract address or identifier for the token asset. Data type: STRING. This field contains the unique address where the token contract is deployed on its respective blockchain network. Used for token identification, contract verification, cross-chain asset mapping, and blockchain-specific operations. Example: ‘0xa0b86a33e6441b8c4c8c8c8c8c8c8c8c8c8c8c8c’ for USDC on Ethereum, NULL for native assets like Bitcoin or Flow. Critical for DeFi operations, smart contract interactions, and maintaining accurate token mappings across different blockchain networks. |
| SYMBOL | TEXT | The ticker symbol or abbreviated code representing the asset. Data type: STRING. This field contains the short, standardized identifier used in trading, price displays, and market data. Used for quick asset identification, trading interfaces, price feeds, and cross-platform asset matching. Example: ‘BTC’ for Bitcoin, ‘ETH’ for Ethereum, ‘FLOW’ for Flow, ‘USDC’ for USD Coin. Critical for market data integration, trading operations, and maintaining consistency across different exchanges and price providers. |
| NAME | TEXT | |
| DECIMALS | NUMBER | The number of decimal places used to represent the smallest unit of the asset. Data type: INTEGER. This field indicates the precision with which the asset can be divided and is essential for accurate price calculations and token amount conversions. Used for token amount normalization, price precision calculations, and ensuring accurate financial computations. Example: 18 for most ERC-20 tokens, 8 for Bitcoin, 6 for USDC. Critical for DeFi operations, token transfers, and maintaining precision in financial calculations across different blockchain networks. |
| PRICE | FLOAT | The closing price of the asset for the specified hour, denominated in USD. Data type: FLOAT. This field represents the final trading price of the asset during the hour and is used for price analysis, portfolio valuation, and market performance calculations. Used for price trend analysis, asset valuation, and financial reporting. Example: 45000.50 for Bitcoin price at $45,000.50 USD per BTC. Critical for portfolio management, price impact analysis, and maintaining accurate financial records for trading and investment operations. |
| BLOCKCHAIN | TEXT | The blockchain network or platform where the asset is native or primarily traded. Data type: STRING. This field identifies the specific blockchain ecosystem that hosts the asset’s smart contract or where the native asset operates. Used for cross-chain analytics, multi-chain portfolio tracking, and blockchain-specific filtering and grouping. Example: ‘ethereum’ for ETH and ERC-20 tokens, ‘flow’ for FLOW and Flow-native assets, ‘bitcoin’ for BTC. Critical for understanding asset distribution across blockchain networks, cross-chain bridge analysis, and multi-chain DeFi analytics. |
| IS_NATIVE | BOOLEAN | A boolean flag indicating whether the asset is the native token of its respective blockchain network. Data type: BOOLEAN. This field distinguishes between native blockchain tokens and smart contract-based tokens. Used for filtering native vs. token assets, blockchain-specific analytics, and understanding asset distribution across different token types. Example: TRUE for Bitcoin (BTC), Ethereum (ETH), and Flow (FLOW), FALSE for USDC, DAI, and other smart contract tokens. Important for blockchain economics analysis, native token price tracking, and understanding the relationship between native tokens and their ecosystem tokens. |
| IS_IMPUTED | BOOLEAN | A boolean flag indicating whether the price data was imputed or derived from previous records rather than being directly observed. Data type: BOOLEAN. This field helps identify price data that may be less reliable due to low liquidity or inconsistent reporting from the source. Used for data quality assessment, filtering out potentially unreliable price data, and understanding data completeness. Example: TRUE for low-liquidity tokens with infrequent trading, FALSE for actively traded assets with regular price updates. Critical for data quality management, risk assessment, and ensuring accurate price analysis for trading and investment decisions. |
| IS_DEPRECATED | BOOLEAN | A boolean flag indicating whether the asset has been deprecated or is no longer actively supported by the price provider. Data type: BOOLEAN. This field helps identify assets that may have outdated or unreliable price data. Used for data quality filtering, identifying discontinued assets, and ensuring data reliability in analytics and trading operations. Example: TRUE for deprecated tokens or assets no longer listed on exchanges, FALSE for actively traded assets. Critical for data quality management, avoiding stale price data, and maintaining accurate market analytics. |
| IS_VERIFIED | BOOLEAN | |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. |
| EZ_PRICES_HOURLY_ID | TEXT | pk_id is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. |
