ethereum.nft Table: ez_nft_sales Type: View
What
This table provides a comprehensive view of NFT (Non-Fungible Token) sales across all major marketplaces and platforms on EVM blockchains. It captures both direct marketplace sales and aggregator-routed transactions, enabling analysis of NFT market dynamics, collection performance, and trading patterns.Key Use Cases
- Analyze daily/weekly NFT market volume and trends by platform
- Track top-performing NFT collections by sales count and volume
- Monitor marketplace competition and market share analysis
- Identify whale activity and buyer behavior patterns
- Evaluate creator royalty enforcement across platforms
- Assess fee structures and revenue models by marketplace
- Track cross-platform trader behavior and platform preferences
Important Relationships
- Links to
core.fact_event_logsviatx_hashandevent_index - Joins with
core.dim_contractsfor collection name - References
price.ez_prices_hourlyfor currency conversions - Connects to token transfer tables for ownership tracking
Commonly-used Fields
platform_name: Marketplace where sale occurred (opensea, blur, etc.)contract_address: NFT collection contract addresstoken_id: Unique identifier of the specific NFTbuyer_address/seller_address: Transaction participantsprice_usd: Sale price converted to USD (includes fees)total_fees_usd: Combined platform and creator fees in USDevent_type: Type of sale transaction (sale, bid_won, etc.)
Sample Queries
Daily NFT market volume by platformColumns
| Column Name | Data Type | Description |
|---|---|---|
| BLOCK_NUMBER | NUMBER | Sequential counter representing the position of a block in the blockchain since genesis (block 0). |
- Immutable once finalized
- Primary ordering mechanism for blockchain data
- Increments by 1 for each new block
- Used as a proxy for time in many analyses
- Set by block producer
- Can have minor variations (±15 seconds)
- Always increasing (newer blocks = later timestamps)
- Primary key for transaction lookups
- Join key for traces, logs, and token transfers
- Immutable once confirmed
0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060 | | EVENT_INDEX |
FLOAT | Zero-based sequential position of the event within a transaction’s execution.
Key Facts:
- Starts at 0 for first event
- Increments across all contracts in transaction
- Preserves execution order
- Essential for deterministic event ordering
- 0xa9059cbb: transfer(address,uint256)
- 0x095ea7b3: approve(address,uint256)
- 0x23b872dd: transferFrom(address,address,uint256)
- Deduplication in incremental loads
- Join operations for data quality checks
- Troubleshooting specific records
- Data freshness monitoring
- Incremental processing markers
- Debugging data pipeline issues
- SLA tracking