Native Transfer Event

Native transfer event data example and explaination

When a native transfer 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:

{
  "chain": "Avalanche",
  "monitorId": "mo_zzn4ntlNbuyEs18d",
  "hash": "0xd7af0b3df64283d569645d2f19f210c05af17bc56161c3e78fd2748a9615b4f3",
  "blockNum": 45835989,
  "fromAddress": "0xbbf9a038fa904895f0fd907337dec1f156effab2",
  "toAddress": "0xbbf9a038fa904895f0fd907337dec1f156effab2",
  "nativeAmount": "123000000000000000",
  "type": "in",
  "confirm": false,
  "category": "Native",
  "dateCreated": "2024-05-24T09:41:52.193Z",
  "txnIndex": 1,
  "associatedAddress": "0xbbf9a038fa904895f0fd907337dec1f156effab2",
  "eventId": "70ee1f489c9746549dd35af289ba86e7",
  "tags": []
}

Data Explanation

• chain: The blockchain network where the event occurred (e.g., Avalanche)

• monitorId: Unique identifier for the monitor that captured the event.

• hash: Transaction hash associated with the event.

• blockNumber: Block number in which the transaction was included.

• fromAddress: Address from which the native cryptocurrency was sent.

• toAddress: Address to which the native cryptocurrency was sent.

• nativeAmount: Amount of native cryptocurrency transferred (in the smallest unit, e.g., wei for ETH).

• type: Transaction type (e.g., "in" for incoming).

• confirm: Boolean indicating whether the transaction is confirmed.

• category: Type of transfer (e.g., Native for native cryptocurrency).

• dateCreated: Timestamp of when the event was detected.

• 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 (if any).