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

​
Description

This table provides enriched NFT sales data for Aptos, combining raw on-chain sale 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 sales activity and marketplace trends in USD
  • Building dashboards for NFT sales volume, user activity, and project performance
  • Comparing sales activity across projects, platforms, and tokens
  • Supporting NFT research, monitoring, and reporting
  • Powering downstream models for NFT aggregations and analytics

​
Important Relationships

  • Sources raw sales data from nft.fact_nft_sales
  • 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 mint data in nft.ez_nft_mints for lifecycle analysis

​
Commonly-used Fields

  • tx_hash, event_index: Unique identifiers for each sale event
  • nft_address, tokenid: NFT contract and token identifiers
  • seller_address, buyer_address: Addresses involved in the sale
  • block_timestamp: Time of the sale event
  • project_name, platform_name: Names of the NFT project and marketplace
  • total_price, total_price_usd: Decimal-adjusted and USD value of sale price
  • platform_fee, creator_fee, total_fees: Fee amounts in both raw and USD terms

​
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.
BUYER_ADDRESSTEXTThe address of the buyer of the NFT in the transaction.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Used for tracking NFT buyers and purchase activity.
  • Enables user-level analytics, purchase reporting, and marketplace analysis.
  • Supports linking to address labels and user profiles. | | SELLER_ADDRESS | TEXT | | | NFT_ADDRESS | TEXT | The contract address of the NFT. | | TOKEN_VERSION | TEXT | The version of the NFT token. | | PLATFORM_ADDRESS | TEXT | The contract address of the NFT marketplace or platform where the event occurred.
Data type: String Example:
  • 0x1::marketplace::Marketplace
  • 0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890
Business Context:
  • Used for identifying NFT marketplaces and platforms.
  • Enables platform-level analytics, filtering, and reporting.
  • Supports joining with metadata and project information. | | 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. | | PLATFORM_NAME | TEXT | The name of the NFT marketplace or platform where the event occurred.
Data type: String Example:
  • bluemove
  • topaz
  • souffl3
Business Context:
  • Used for grouping and filtering NFT events by platform.
  • Enables platform-level analytics, trend analysis, and reporting.
  • Supports dashboards and user-facing NFT discovery tools. | | PLATFORM_EXCHANGE_VERSION | TEXT | The version or identifier of the NFT marketplace or platform where the event occurred.
Data type: String Example:
  • v1
  • v2
  • 2023-01-01
Business Context:
  • Used for tracking platform upgrades, changes, and event context.
  • Enables version-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. | | PLATFORM_FEE | FLOAT | The platform fee paid as part of the NFT sale or mint, in decimal-adjusted units of the transaction currency.
Data type: Decimal Example:
  • 0.01 (for 1 cent fee)
  • 2.5 (for 2.5 units of the transaction currency)
Business Context:
  • Used for analyzing platform revenue and fee structures.
  • Enables comparison of platform fees across projects, platforms, and time.
  • Supports dashboards and business intelligence for NFT marketplaces. | | PLATFORM_FEE_USD | FLOAT | The platform fee paid as part of the NFT sale or mint, converted to USD at the time of the transaction.
Data type: Decimal Example:
  • 0.01 (for $0.01 fee)
  • 2.5 (for $2.50 fee)
Business Context:
  • Used for analyzing platform revenue and fee structures in USD terms.
  • Enables comparison of platform fees across projects, platforms, and time.
  • Supports dashboards and business intelligence for NFT marketplaces. | | CREATOR_FEE | FLOAT | The creator royalty fee paid as part of the NFT sale or mint, in decimal-adjusted units of the transaction currency.
Data type: Decimal Example:
  • 0.01 (for 1 cent fee)
  • 2.5 (for 2.5 units of the transaction currency)
Business Context:
  • Used for analyzing creator revenue and royalty structures.
  • Enables comparison of creator fees across projects, platforms, and time.
  • Supports dashboards and business intelligence for NFT marketplaces. | | CREATOR_FEE_USD | FLOAT | The creator royalty fee paid as part of the NFT sale or mint, converted to USD at the time of the transaction.
Data type: Decimal Example:
  • 0.01 (for $0.01 fee)
  • 2.5 (for $2.50 fee)
Business Context:
  • Used for analyzing creator revenue and royalty structures in USD terms.
  • Enables comparison of creator fees across projects, platforms, and time.
  • Supports dashboards and business intelligence for NFT marketplaces. | | TOTAL_FEES | FLOAT | The total amount of fees paid relating to the NFT purchase, in decimal-adjusted units. This includes royalty payments to creators and platform fees, but does not include the gas fee.
Data type: Decimal Example:
  • 0.01 (for 1 cent fee)
  • 2.5 (for 2.5 units of the transaction currency)
Business Context:
  • Used for financial analysis and reporting of NFT fee structures.
  • Enables comparison of fee burdens across projects, platforms, and time.
  • Supports dashboards and business intelligence for NFT marketplaces. | | TOTAL_FEES_USD | FLOAT | The total amount of fees paid relating to the NFT purchase, converted to USD. This includes royalty payments to creators and platform fees, but does not include the gas fee.
Data type: Decimal Example:
  • 0.01 (for 1 cent fee)
  • 2.5 (for $2.50 fee)
Business Context:
  • Used for financial analysis and reporting of NFT fee structures in USD terms.
  • Enables comparison of fee burdens across projects, platforms, and time.
  • Supports dashboards and business intelligence for NFT marketplaces. | | AGGREGATOR_NAME | TEXT | The name of the NFT aggregator or routing service involved in the event, if applicable.
Data type: String Example:
  • Gem
  • Genie
  • None
Business Context:
  • Used for grouping and filtering NFT events by aggregator.
  • Enables aggregator-level analytics, trend analysis, and reporting.
  • Supports dashboards and user-facing NFT discovery tools. | | 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_SALES_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. |