Skip to main content
Schema: aptos.nft Table: ez_nft_mints Type: View

Description

This table provides enriched NFT mint data for Aptos, combining raw on-chain mint events with token metadata (symbols, decimals) and price information. It includes decimal-adjusted prices, token symbols, and USD values, making it suitable for analytics and reporting.

Key Use Cases

  • Analyzing NFT minting activity and project launches in USD
  • Building dashboards for NFT mint volume, user activity, and project trends
  • Comparing mint activity across projects and tokens
  • Supporting NFT research, monitoring, and reporting
  • Powering downstream models for NFT aggregations and analytics

Important Relationships

  • Sources raw mint data from nft.fact_nft_mints
  • Joins token metadata from core.dim_tokens for symbol/decimals
  • Joins price data from price.ez_prices_hourly for USD values
  • Can be related to NFT sales data in nft.ez_nft_sales for lifecycle analysis

Commonly-used Fields

  • tx_hash, event_index: Unique identifiers for each mint event
  • nft_address, tokenid: NFT contract and token identifiers
  • nft_from_address, nft_to_address: Addresses involved in the mint
  • block_timestamp: Time of the mint event
  • project_name: Name of the NFT project
  • total_price, total_price_usd: Decimal-adjusted and USD value of mint price

Columns

Column NameData TypeDescription
BLOCK_TIMESTAMPTIMESTAMP_NTZThe block timestamp at which the NFT event occurred.
BLOCK_NUMBERNUMBERThe block number at which the NFT event occurred.
VERSIONNUMBER
TX_HASHTEXTThe transaction hash for the NFT event. This is not necessarily unique in this table as a transaction may contain multiple NFT events.
EVENT_INDEXNUMBERThe event number within a transaction
EVENT_TYPETEXTThe type of NFT event in this transaction, either sale, bid_won or redeem.
NFT_FROM_ADDRESSTEXTThe account address that sent or originated the NFT in a mint or transfer event.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Used for tracking NFT creators, senders, and transferors.
  • Enables user-level analytics, provenance, and ownership history.
  • Supports linking to address labels and user profiles. | | NFT_TO_ADDRESS | TEXT | The account address that received the NFT in a mint or transfer event.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Used for tracking NFT recipients, buyers, and new owners.
  • Enables user-level analytics, ownership history, and transfer analysis.
  • Supports linking to address labels and user profiles. | | NFT_ADDRESS | TEXT | The contract address of the NFT. | | TOKEN_VERSION | TEXT | The version of the NFT token. | | PROJECT_NAME | TEXT | The name of the NFT project. This field, along with metadata, will be filled in over time. | | TOKENID | TEXT | The token ID for this NFT contract. | | NFT_COUNT | NUMBER | The number of NFTs minted in this event.
Data type: Integer Example:
  • 1
  • 10
Business Context:
  • Used for quantifying NFT minting activity and project launches.
  • Enables project-level analytics, trend analysis, and reporting.
  • Supports dashboards and user-facing NFT discovery tools. | | TOTAL_PRICE | FLOAT | The price of the NFT event (mint or sale), in decimal-adjusted units of the transaction currency.
Data type: Decimal Example:
  • 1.0 (for 1 unit of the transaction currency)
  • 0.25 (for 0.25 units of the transaction currency)
Business Context:
  • Used for financial analysis, reporting, and cross-project comparisons.
  • Enables value-based analytics and aggregation of NFT volumes in native currency terms.
  • Supports dashboards and business intelligence for NFT marketplaces. | | TOTAL_PRICE_USD | FLOAT | The price of the NFT event (mint or sale), converted to USD at the time of the transaction.
Data type: Decimal Example:
  • 100.00 (for $100 sale)
  • 0.50 (for $0.50 mint)
Business Context:
  • Used for financial analysis, reporting, and cross-project comparisons.
  • Enables value-based analytics and aggregation of NFT volumes in USD terms.
  • Supports dashboards and business intelligence for NFT marketplaces. | | CURRENCY_ADDRESS | TEXT | The contract address of the currency used for the NFT event (mint or sale).
Data type: String Example:
  • 0x1::aptos_coin::AptosCoin
  • 0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890
Business Context:
  • Used for identifying the payment currency for NFT events.
  • Enables currency-level analytics, filtering, and reporting.
  • Supports joining with token metadata and price information. | | EZ_NFT_MINTS_ID | TEXT | The unique primary key identifier for each row in the table, ensuring data integrity and uniqueness.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for data integrity and unique row identification.
  • Critical for join operations and data relationship management.
  • Enables precise data retrieval and referential integrity maintenance. | | 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. |