Skip to main content
Schema: somnia.price Table: fact_prices_ohlc_hourly Type: Base Table

​
What

This table provides hourly OHLC (Open, High, Low, Close) price data for all assets tracked in the price schema. It is designed for time series analysis, volatility studies, and historical price lookups.

​
Key Use Cases

  • Technical analysis and candlestick chart creation
  • Volatility studies and risk assessment
  • Historical price lookups and trend analysis
  • Market timing and trading analysis

​
Important Relationships

  • Join with dim_asset_metadata: For asset metadata
  • Join with ez_token_transfers: For USD value calculations

​
Commonly-used Fields

  • hour: UTC timestamp for the price period
  • asset_id: Unique identifier for the asset
  • open: Opening price at start of hour
  • high: Highest price during hour
  • low: Lowest price during hour
  • close: Closing price at end of hour

​
Sample Queries

OHLC Data Retrieval 
SELECT hour, asset_id, open, high, low, close
FROM <blockchain_name>.price.fact_prices_ohlc_hourly
WHERE asset_id = '<asset_id>'
  AND hour >= CURRENT_DATE - 30
ORDER BY hour DESC;

​
Columns

Column NameData TypeDescription
ASSET_IDTEXTUnique identifier for the asset from the price provider. Provider-specific ID format. Example: ‘ethereum’
HOURTIMESTAMP_NTZUTC timestamp truncated to the hour for price recording. Used for joining with hourly transaction data. Example: ‘2024-01-15 14:00:00.000’
OPENFLOATOpening price at the start of the hour in USD. First recorded price in the hour for OHLC analysis. Example: 2995.25
HIGHFLOATHighest price reached during the hour in USD. Maximum price in the hour for volatility analysis. Example: 3005.75
LOWFLOATLowest price reached during the hour in USD. Minimum price in the hour for support level analysis. Example: 2985.50
CLOSEFLOATClosing price at the end of the hour in USD. Last recorded price in the hour, commonly used for valuations. Example: 3000.50
PROVIDERTEXTPROVIDER column
FACT_PRICES_OHLC_HOURLY_IDTEXTPrimary 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_TIMESTAMPTIMESTAMP_NTZUTC 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_TIMESTAMPTIMESTAMP_NTZUTC 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: