core-chain.nft Table: ez_nft_transfers Type: Base Table
What
This table contains all NFT transfer events for ERC-721 and ERC-1155 tokens on EVM blockchains. It provides a comprehensive view of NFT movements including transfers, mints, and burns, with enriched metadata for easier analysis.Key Use Cases
- Track daily NFT activity and transfer volume across collections
- Analyze NFT minting patterns and mint timing
- Identify popular collections by transfer activity
- Monitor wallet NFT accumulation and trading behavior
- Analyze ERC-1155 batch transfer patterns
- Track current NFT holders and ownership changes
- Detect burns and unusual transfer patterns
Important Relationships
- Join with ez_nft_sales: Use
tx_hashto match with sales but note that a single transaction can contain multiple sales. Do not useevent_indexto match as theevent_indexin ez_nft_transfers represent theevent_indexof the transfer and not the sale - Join with dim_nft_collection_metadata: This is only for the Ethereum blockchain. Use
contract_addressandtoken_idfor metadata like traits, token id name and token id description - Join with fact_transactions: Use
tx_hashfor transaction context
Commonly-used Fields
contract_address: NFT collection contract addresstoken_id: Unique identifier of the specific NFTfrom_address/to_address: Transfer participants (0x0 for mint/burn)is_mint: Boolean flag for minting eventstoken_standard: NFT standard (erc721, erc1155, cryptopunks, legacy)nft_quantity: Number of tokens transferred (always 1 for ERC-721)token_transfer_type: Specific event type emitted
Sample Queries
Daily NFT Activity OverviewColumns
| 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 | | TX_POSITION |
NUMBER | Zero-indexed position of transaction within its block.
Insights:
- Position 0: First transaction in block
- MEV bots often target early positions
- Bundle transactions appear consecutively
- Useful for analyzing transaction ordering | | EVENT_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution.
- Starts at 0 for first event
- Increments across all contracts in transaction
- Preserves execution order
- Essential for deterministic event ordering
- 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