Skip to main content
Schema: tron.price Table: dim_asset_metadata Type: Base Table

​
What

This table provides provider-level metadata for all assets tracked in the price schema on Tron. It includes the price provider, asset identifiers, names, symbols, contract addresses, and blockchain information.

​
Key Use Cases

  • Cross-referencing asset IDs across different price providers
  • Asset discovery and provider-specific data analysis
  • Mapping token addresses to provider identifiers

​
Important Relationships

  • Join with ez_prices_hourly: Use asset_id for price time series
  • Join with fact_prices_ohlc_hourly: Use asset_id for OHLC data
  • Join with fact_asset_metrics_daily: Use asset_id for market data

​
Commonly-used Fields

  • provider: Data source (coingecko, coinmarketcap, etc.)
  • asset_id: Provider-specific unique identifier
  • blockchain: Network identifier
  • token_address: Contract address (NULL for native assets)
  • symbol: Token ticker symbol

​
Sample queries

-- All Tron assets tracked by provider
SELECT
    provider,
    asset_id,
    symbol,
    name,
    token_address
FROM tron.price.dim_asset_metadata
ORDER BY symbol;

​
Columns

Column NameData TypeDescription
TOKEN_ADDRESSTEXTContract address of the token on the blockchain, in 0x-prefixed hex format. NULL for native TRX. Example: ‘0xa614f803b6fd780986a42c78ec9c7f77e6ded13c’
ASSET_IDTEXTUnique identifier for the asset from the upstream price provider. Example: ‘tron’
SYMBOLTEXTToken ticker symbol as commonly recognized. Example: ‘USDT’
NAMETEXTFull name of the asset or token. Example: ‘Tether USD’
BLOCKCHAINTEXTThe blockchain network where the asset exists. Example: ‘tron’
BLOCKCHAIN_IDTEXTThe numeric or string identifier for the blockchain on which the asset exists. Used for cross-chain mapping. Example: ‘tron’
PROVIDERTEXTData source that provided the price information. Values include ‘coingecko’, ‘coinmarketcap’, ‘dex_aggregated’. Example: ‘coingecko’
DIM_ASSET_METADATA_IDTEXTPrimary key — unique identifier for each row ensuring data integrity. Format: VARCHAR containing composite key generated using MD5 hash of the relevant columns. Usage: Deduplication in incremental loads Join operations for data quality checks Troubleshooting specific records
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
MODIFIED_TIMESTAMPTIMESTAMP_NTZUTC timestamp of the most recent update to this record. Format: TIMESTAMP_NTZ Use Cases: Tracking data corrections and reprocessing Monitoring incremental model updates Data quality audits