Documentação

English

Português
Español

English

Português
Español

Appearance

NFT Blockchain Transactions (Journal) ​

Access prerequisites

  • Permission (module): viewNftTransactionsJournal
  • License/Feature: None
  • Menu container: GENERAL → group Transaction journals → NFT Blockchain Transactions (/nft-blockchain-transactions-journal)

What it is / when to use ​

Records the on-chain events of NFTs processed by the platform: issuance (mint), transfer (transfer), and other asset movements on the blockchain, along with the seller, buyer, asset, and transaction hash. Use this screen to confirm that an NFT was actually minted/transferred on the network, retrieve the transaction_hash to look up in a blockchain explorer, and diagnose pending deliveries.

Prerequisites ​

  • Permission: viewNftTransactionsJournal (dual permission — CPM enum + dynamic module in DB).
  • License/Feature: none.
  • Dependencies on other screens: None. Events come from TokenController/ExternalBlockchainProvider (on-chain watcher).

Step by step ​

  1. Go to Transaction journals → NFT Blockchain Transactions.
  2. Fill in one or more filters: Asset ID, Buyer ID, Seller ID (search has a 400 ms debounce; Apply and Clear buttons are also available).
  3. Click View details to open the dialog with the hash and full event data.

Filters and columns ​

Filter / ColumnWhat it shows / doesData source
Asset ID filterRestricts to a given asset_id.filters.assetId.
Buyer ID filterRestricts to a given buyerId.filters.buyerId.
Seller ID filterRestricts to a given sellerId.filters.sellerId.
Date (createdOn)When the event was recorded.created_on.
Asset (assetId)NFT/asset identifier.asset_id.
Type (transactionType)mint, transfer (translated); other types displayed as received.transaction_type.
Seller (seller)Resolved email/name of the seller (or raw ID).seller_id (resolved via user registry).
Buyer (buyer)Resolved email/name of the buyer (or raw ID).buyer_id.
ActionsOpens the details dialog.openTransactionDetails(transaction).

Additional fields in the dialog ​

FieldWhat it shows
Blockchain IDnft_blockchain_id — the on-chain token ID.
Transaction hashtransaction_hash — for lookup in the network explorer.
Reason (reason)Reason/context of the event (e.g.: crowdfunding mint, burn).
Executed at (executed_on)When the event was finalized on-chain (may differ from created_on).

Actions and modals ​

  • View details: opens TransactionDetailsDialogComponent, read-only, with the hash, on-chain IDs, and already-resolved buyer/seller labels.

Business rules / notes ​

Attention

  • The difference between created_on (recording) and executed_on (on-chain finalization) indicates confirmation latency. An event with created_on but no executed_on is still pending on the network.
  • For crowdfunding NFTs, the mint is exclusive to the crowdfunding job (no ad-hoc issuance by the token owner). A mint here must always have a reason consistent with the origin.
  • In an NFT burn, the on-chain event can be a NATIVE_BURN (v2 contracts) or a transfer to the BURN_SINK sink wallet (v1). The buyer/destination is therefore not a user but the sink — do not confuse this with a regular transfer.
  • This screen is read-only: it does not trigger mint/transfer/burn. Issuance/burn operations are performed on the Tokenization screens.