Skip to main content
Schema: near.nft Table: fact_nft_mints Type: View

​
Description

This table contains all NFT minting transactions on the NEAR Protocol blockchain, capturing the creation of new NFTs across various collections and standards. The data includes minting details such as token IDs, minting methods, arguments, deposits, and associated metadata. This table provides the foundation for NFT analytics, collection growth tracking, and minting pattern analysis across the NEAR ecosystem.

​
Key Use Cases

  • NFT collection growth analysis and minting velocity tracking
  • NFT minting pattern analysis and user behavior monitoring
  • Collection launch analysis and initial distribution tracking
  • NFT minting cost analysis and gas optimization
  • Cross-collection minting comparison and performance benchmarking
  • NFT creator analysis and minting strategy evaluation
  • NFT ecosystem health monitoring and collection discovery

​
Important Relationships

  • Links to core.fact_transactions through tx_hash for transaction context
  • Connects to core.fact_blocks through block_id for temporal context
  • Provides minting data for nft.ez_nft_sales with enhanced metadata
  • Supports nft.fact_nft_transfers with minting context
  • Enables analysis in stats.ez_core_metrics_hourly for NFT metrics
  • Powers cross-collection analysis and ecosystem mapping

​
Commonly-used Fields

  • tx_hash: Essential for linking to transaction details and verification
  • block_timestamp: Primary field for time-series analysis and trend detection
  • token_id: Critical for unique NFT identification and tracking
  • owner_id: Important for creator analysis and ownership tracking
  • method_name: Essential for minting method classification and analysis
  • deposit and implied_price: Important for minting cost analysis
  • tx_receiver: Critical for collection identification and contract analysis

​
Columns

Column NameData TypeDescription
RECEIPT_OBJECT_IDTEXTPlease note this column is being deprecated in favor of simply “receipt_id”.
TX_HASHTEXTUnique identifier (hash) of this transaction.
BLOCK_IDNUMBERThe height of the chain this block corresponds with.
BLOCK_TIMESTAMPTIMESTAMP_NTZThe date and time at which the block began.
TOKEN_IDTEXTThe token ID for this NFT contract.
METHOD_NAMETEXTName of the method(s) approved for use. NULL if permission is FullAccess.
ARGSVARIANTDecoded (where possible) arguments passed alongside the method_name. If decoding failed, the table will contain the raw message.
MEMOVARIANTOptional log message within the transaction (often null). This field contains additional information or context about the transfer, such as transaction notes, reference numbers, or descriptive text. Memos are commonly used in cross-chain bridges, exchange deposits, or other scenarios where additional context is needed to identify or process the transfer. The memo field is optional and frequently null for standard transfers.
DEPOSITNUMBERSum of all NEAR tokens transferred from the signing account to the receiver account during receipt processing. This includes tokens sent in a Transfer action(s), and tokens sent in a FunctionCall action(s) with a deposit attached.
In raw number format with 24 decimal places, to adjust divide by POW(10,24) or multiply by 1e-24. | | TX_RECEIVER | TEXT | | | RECEIVER_ID | TEXT | Account reacting to the receipt from predecessor_id, can be relay, a contract, or a user of a relay, etc. This field identifies the account that is processing the receipt and executing the associated action. In most cases, this is a smart contract that is being called, but it can also be a user account in relay transactions or the system account for certain operations. This differs from tx_receiver and is specific to the receipt being processed. | | SIGNER_ID | TEXT | Signer of the receipt, often same as tx_signer, sometimes system in the case of systemic gas refunds. This field identifies the account that has the authority to execute the receipt. In most cases, this is the same as the transaction signer, but in system operations like gas refunds, this may be the system account. The signer is the account that originally signed the transaction that began the blockchain activity, which may or may not include cross-contract calls. | | OWNER_ID | TEXT | Owner of the minted NFT | | OWNER_PER_TX | NUMBER | Number of different owners batch minting, data array’s len in the LOG message | | MINT_PER_TX | NUMBER | Number of NFTs minted per nft_mint event called. | | GAS_BURNT | NUMBER | Gas burned for the receipt action. This field represents the amount of computational resources consumed specifically for the receipt being processed. Gas burning is the mechanism by which NEAR charges for computational work, and this field tracks the exact amount burned for this particular receipt action. In raw number format with 16 decimal places, to adjust divide by POW(10,16) or multiply by 1e-16. | | TRANSACTION_FEE | NUMBER | Total fee paid in NEAR to execute this transaction, which is a summation of all fees paid for actions and receipts within the transaction. In raw number format, to adjust divide by POW(10,24) | | IMPLIED_PRICE | FLOAT | | | TX_STATUS | TEXT | | | TX_SUCCEEDED | BOOLEAN | Boolean indicating if the transaction was successful (rarely used, most tx succeed, it is receipts that can fail). This field tracks the overall success status of the transaction. While most transactions succeed at the transaction level, individual receipts within the transaction can still fail. This field is less commonly used for filtering since receipt-level success tracking provides more granular information about specific operations within the transaction. | | MINT_ACTION_ID | TEXT | | | FACT_NFT_MINTS_ID | TEXT | A unique identifier for the record. | | INSERTED_TIMESTAMP | TIMESTAMP_LTZ | The timestamp at which the record was initially created and inserted into this table. | | MODIFIED_TIMESTAMP | TIMESTAMP_LTZ | The timestamp at which this record was last modified by an internal process. |