Skip to main content
Schema: aptos.core Table: dim_tokens Type: Base Table

​
Description

This table serves as the comprehensive token metadata dimension for the Aptos blockchain, combining information from both legacy coin tokens and newer fungible assets. It provides essential token characteristics including names, symbols, decimal precision, creator addresses, and creation timestamps. The table unifies metadata from two different token standards on Aptos: the original coin module and the newer fungible asset module, ensuring complete coverage of all tokens on the network for analytics and display purposes.

​
Key Use Cases

  • Token identification and display with human-readable names and symbols
  • Decimal conversion for accurate financial calculations in transfer analysis
  • Token creation analysis and creator address tracking
  • Token verification and metadata validation for data quality
  • Token discovery and categorization for DeFi and NFT analytics
  • Historical token creation timeline analysis

​
Important Relationships

  • Enriches transfer data in core.fact_transfers and core.ez_transfers with token metadata
  • Provides decimal information for proper amount calculations in transfer analytics
  • Supports token verification processes and quality assessment
  • Links to creator addresses for token origin analysis
  • Enables token categorization and filtering across all core models

​
Commonly-used Fields

  • token_address: Primary identifier for linking to transfer and transaction data
  • symbol: Human-readable token symbol for easy identification and filtering
  • decimals: Critical for proper decimal conversion in financial calculations
  • name: Full token name for display and identification purposes
  • creator_address: Important for token origin analysis and creator tracking
  • transaction_created_timestamp: Essential for token creation timeline analysis

​
Columns

Column NameData TypeDescription
TOKEN_ADDRESSTEXTThe full address of the token on the Aptos blockchain, containing the account, module, and resource identifiers.
Data type: String Example:
  • 0x1::coin::AptosCoin (native APT token)
  • 0xf22bede237a07e121b56d91a491eb7bcdfd1f5907926a9e58338f964a01b17fa::coin::USDC
Business Context:
  • Primary identifier for filtering and grouping transactions by specific tokens.
  • Essential for DeFi analysis, token flow tracking, and protocol-specific analytics.
  • Enables correlation with token metadata for symbol and decimal information. | | NAME | TEXT | The full name of the token, providing a human-readable identifier for the asset.
Data type: String Example:
  • Aptos Coin
  • USD Coin
  • Tether USD
Business Context:
  • Essential for token identification and human-readable reporting.
  • Critical for token categorization and name-based filtering.
  • Enables user-friendly analytics and token name analysis. | | SYMBOL | TEXT | The symbol of the token involved in the action (e.g., APT, USDC, USDT). Used to identify the asset type in analytics and reporting.
Data type: String Example:
  • APT
  • USDC
  • USDT
Business Context:
  • Enables grouping and filtering of transfers by token.
  • Supports analytics on asset flows, protocol usage, and user preferences.
  • Provides human-readable identification for tokens in reports and dashboards. | | DECIMALS | NUMBER | The number of decimal places used for the token’s precision, determining the smallest unit of the token.
Data type: Integer Example:
  • 8 (Bitcoin-style precision)
  • 18 (Ethereum-style precision)
  • 6 (USDC-style precision)
Business Context:
  • Essential for accurate token amount calculations and decimal adjustment.
  • Critical for price calculations and financial reporting accuracy.
  • Enables precise token analytics and amount conversion operations. | | COIN_TYPE_HASH | TEXT | The cryptographic hash of the coin type, providing a unique identifier for the token’s type definition.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for token type identification and uniqueness verification.
  • Critical for token categorization and type-based analysis.
  • Enables type-based analytics and token classification. | | CREATOR_ADDRESS | TEXT | The account address that created the token, representing the original issuer of the asset.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for token origin tracking and creator analysis.
  • Critical for token issuer identification and creation verification.
  • Enables creator-based analytics and token origin analysis. | | TRANSACTION_CREATED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when the token was created, representing when the token was first deployed on the blockchain.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for token age analysis and creation timing tracking.
  • Critical for token lifecycle analysis and creation event correlation.
  • Enables creation-based analytics and token age reporting. | | TRANSACTION_VERSION_CREATED | NUMBER | The transaction version when the token was created, representing the specific transaction that deployed the token.
Data type: Integer Example:
  • 12345678
  • 98765432
Business Context:
  • Essential for token creation transaction identification and version tracking.
  • Critical for token deployment analysis and creation transaction correlation.
  • Enables version-based analytics and creation transaction reporting. | | DIM_TOKEN_ID | TEXT | | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was inserted into the table, representing when the data was first recorded.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data lineage tracking and insertion timing analysis.
  • Critical for understanding data freshness and processing delays.
  • Enables data quality analysis and processing performance monitoring. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was last modified, representing when the data was most recently updated.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data freshness analysis and update tracking.
  • Critical for understanding data modification patterns and change frequency.
  • Enables data quality monitoring and update performance analysis. |