Crypitor
Home
  • Overview
    • Introduction
    • Blockchain limitations
    • Our solution
    • Techstack
    • Benefit
    • Use cases
      • Transaction Monitoring
      • DApp Integration
      • Cross-Chain Communication
      • Payment system
      • Security Alerts
  • How To Use
    • Create Monitor
    • Native Transfer Event
    • Erc20 Transfer Event
    • Erc721 Transfer Event
  • Webhook
    • Deliveries
  • Network
    • Supported Networks
    • Webhook Delivery for Confirmations
  • Self Hosted
    • Quick start
    • Creating a Monitor
    • Start Development
Powered by GitBook
On this page

Was this helpful?

  1. How To Use

Erc20 Transfer Event

ERC20 (Token) transfer event data example and explaination

When an ERC20 token transfer event occurs, Crypitor will send a JSON payload to your webhook endpoint. Below is an example of such a payload for a native transfer:

Example Payload:

{
  "chain": "Polygon",
  "monitorId": "mo_9D6x28TXjI5TxfZp",
  "hash": "0x964d309e9df1ef0a898fa895a07d2dc4c47965671a2d4087d2648b9191ad6a58",
  "blockNumber": 57521001,
  "contract": {
    "address": "0x2791bca1f2de4661ed88a30c99a7a9449aa84174",
    "name": null,
    "symbol": null
  },
  "fromAddress": "0x1075f4967cc15d400013c153cfa3357408973747",
  "toAddress": "0x1075f4967cc15d400013c153cfa3357408973747",
  "tokenValue": "123100",
  "rawLog": {
    "topics": [
      "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
      "0x0000000000000000000000001075f4967cc15d400013c153cfa3357408973747",
      "0x0000000000000000000000001075f4967cc15d400013c153cfa3357408973747"
    ],
    "data": "0x000000000000000000000000000000000000000000000000000000000001e0dc"
  },
  "type": "in",
  "confirm": true,
  "category": "ERC20",
  "dateCreated": "2024-05-29T08:07:37.066Z",
  "logIndex": 413,
  "txnIndex": 88,
  "associatedAddress": "0x1075f4967cc15d400013c153cfa3357408973747",
  "eventId": "6ada205fa1e26721d686e7f7ee0b8366",
  "tags": [
    "crypitor"
  ]
}

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.

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

  • contract: Contains details about the token contract.

    • address: Token contract address.

    • name: Token name (null if not available).

    • symbol: Token symbol (null if not available).

  • fromAddress: Address from which the tokens were sent.

  • toAddress: Address to which the tokens were sent.

  • tokenValue: Amount of tokens transferred (in the smallest unit, e.g., wei for ETH).

  • rawLog: Raw log data from the blockchain.

    • topics: Array of indexed log topics.

    • data: Hex-encoded log data.

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

  • confirm: Boolean indicating whether the transaction is confirmed.

  • category: Type of token transfer (e.g., ERC20).

  • 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.

PreviousNative Transfer EventNextErc721 Transfer Event

Last updated 12 months ago

Was this helpful?