Skip to main content
Schema: sui.price Table: ez_prices_hourly Type: Base Table A convenience table for determining token prices by address and blockchain, and native asset prices by symbol and blockchain. This data set is highly curated and contains metadata for one price per hour per unique asset and blockchain.

​
Columns

Column NameData TypeDescription
HOURTIMESTAMP_NTZHour that the price was recorded at.
TOKEN_ADDRESSTEXTThe specific address representing the asset on a specific platform. This will be NULL if referring to a native asset.
SYMBOLTEXTThe symbol of asset.
NAMETEXT
DECIMALSNUMBERThe number of decimals for the asset. May be NULL.
PRICEFLOATClosing price of the recorded hour in USD.
BLOCKCHAINTEXTThe Blockchain, Network, or Platform for this asset.
IS_NATIVEBOOLEANA flag indicating assets native to the respective blockchain.
IS_DEPRECATEDBOOLEANA flag indicating if the asset is deprecated or no longer supported by the provider.
IS_IMPUTEDBOOLEANA flag indicating if the price was imputed, or derived, from the last arriving record. This is generally used for tokens with low-liquidity or inconsistent reporting.
TOKEN_IS_VERIFIEDBOOLEANBoolean flag indicating whether the token or price record is verified by Flipside’s crosschain curation process. Verified tokens are prioritized for analytics and are considered reliable for most use cases. Unverified tokens may be incomplete, deprecated, or experimental.
EZ_PRICES_HOURLY_IDTEXTUnique identifier for the token metadata record, linking metadata to on-chain token types. Used for metadata management, registry operations, and analytics joins. Example: ‘tokenmeta_123’.
INSERTED_TIMESTAMPTIMESTAMP_NTZTimestamp when the record was inserted into the analytics database. System-generated by the ETL pipeline, typically in TIMESTAMP_NTZ format. Used for data lineage, ETL monitoring, and freshness checks. In Sui analytics, this field is essential for tracking data ingestion latency, validating pipeline health, and supporting incremental model builds. Example: ‘2024-06-01 12:34:56.789’.
MODIFIED_TIMESTAMPTIMESTAMP_NTZTimestamp when the record was last modified in the analytics database. System-generated for change tracking, data versioning, and consistency verification. In Sui, this supports incremental processing, late-arriving data correction, and auditability of analytics workflows. Used to monitor data staleness and trigger downstream updates. Example: ‘2024-06-01 12:34:56.789’.