Erc721 Transfer Event
ERC721 (NFT) transfer event data example and explaination
When an ERC721 NFT event occurs, Crypitor sends a JSON payload to your webhook endpoint. Below is an example of such a payload and an explanation of its structure:
Example Payload:
Data Explanation
chain: The blockchain network where the event occurred (e.g., POLYGON).
monitorId: Unique identifier for the monitor that captured the event.
hash: Transaction hash associated with the event.
blockNum: Block number in which the transaction was included.
contract: Contains details about the NFT contract.
address: NFT contract address.
name: NFT contract name (null if not available).
symbol: NFT contract symbol (null if not available).
fromAddress: Address from which the NFT was transferred. A zero address (
0x0000000000000000000000000000000000000000
) typically indicates a minting event.toAddress: Address to which the NFT was transferred.
tokenId: Unique identifier for the NFT within the contract.
rawLog: Raw log data from the blockchain.
topics: Array of indexed log topics.
data: Hex-encoded log data (empty in this example).
type: Transaction type (e.g., "in" for incoming).
confirm: Boolean indicating whether the transaction is confirmed.
category: Type of transfer (e.g., ERC721 for NFT transfers).
dateCreated: Timestamp of when the event was detected.
logIndex: Position of the log in the block.
txnIndex: Position of the transaction in the block.
associatedAddress: Wallet address associated with the event.
eventId: Unique identifier for the event.
tags: Tags associated with the monitor.
Last updated