Event Type
Supported Event
Event Type | Description |
|---|---|
Monitors the activity of accounts included in a user-specified array of addresses. This event provides notifications whenever those accounts are involved as the sender (from) or recipient (to) of a transaction — including transactions, token transfers (ERC20), or NFT transfers (ERC721, ERC1155). This service enables users to track activity across multiple addresses in real time, helping them effectively monitor asset movements and transactions. | |
Provides the receipt information of a transaction as a notification when a transaction sent by a specific address has been successfully mined and finalized by the blockchain network. This event delivers alerts for both successful and failed transactions. Users can thereby track the final status of their submitted transactions in real time and confirm whether a transaction succeeded or failed. | |
Provides a notification when a transaction sent by a specific address has been successfully processed. This event fires when the transaction is fully confirmed by the blockchain network and determined to be valid. Users can verify that their transaction executed as expected and that the desired operation completed successfully. | |
Provides a notification when a transaction sent by a specific address has failed. This event fires when a transaction is rejected by the blockchain network or could not be completed due to an error during execution. Users can quickly identify the cause of the transaction failure and take the necessary action. Failures can result from various technical issues such as insufficient gas or unmet contract conditions, and this event helps users more effectively manage transactions and track errors on the blockchain. | |
Provides notifications when a token (ERC20) transfer or NFT (ERC721, ERC1155) transfer occurs. Users can specify a particular contract address to monitor token movements from that contract. Additionally, for NFTs following the ERC721 and ERC1155 standards, it is possible to set a specific token ID as a condition to track only transfers of that particular token ID. | |
Provides a notification when the balance of a specified account falls below a threshold value set by the user. This event plays an especially important role in financial management and asset protection. Users can use this feature to take preventive measures so that their account balance does not drop below a minimum level, and can transfer additional funds or take other financial action in a timely manner when needed. | |
Provides notifications according to the period of blocks generated on the network. Users can set a desired block interval (e.g., every block, every N blocks) to receive block information at that interval. This event provides information after a specified number of blocks have been confirmed, delivering more stable and finalized data. | |
Provides a notification when addresses included in a specific block list send tokens to a target address. This event type is primarily used when you want to monitor the activity of addresses on a predefined block list. For example, you can receive an immediate alert when blacklisted addresses attempt to transfer funds to a specific account. This is a useful tool for detecting illegal or suspicious fund movements in advance. | |
Provides a notification when addresses included in an allow list send tokens to a target address. This list contains trusted addresses, and fund movements from those addresses are considered safe or expected activity. This event type is used when you want to track the activity of allowed addresses and confirm fund transfers from addresses included in the allow list. | |
Provides a notification when a transaction containing the specified smart contract event log is created. Users can specify one or more Event signatures as filter conditions. For example, if you configure monitoring for the Transfer(address,address,uint256) token transfer event of the ERC20 standard, all transaction logs matching that Event signature (0xddf252ad...) will be captured. Use the LOG EventType to efficiently track important activities such as standard token transfers or specific smart contract events. |