Transaction Bot Monitoring

What is Transaction Bot Monitoring?

Transaction Bot Monitoring is primarily used for on-chain transaction monitoring.

Typical Scenarios for Transaction Bot Monitoring

  1. Monitor transactions sent by a target sender

  2. Monitor transactions received by a target recipient

  3. Alert when ETH is greater than or less than a specified threshold

  4. Monitor transactions with a specific methodId

Supported Data Sources

Data SourceTypeStability

Ethereum

on chain

Very High

BSC

on chain

High

Avalanche

on chain

High

Polygon Pos

on chain

High

Arbitrum

on chain

High

Optimism

on chain

High

Polygon zkEVM

on chain

High

ZkSync Era

on chain

High

Base

on chain

High

Scroll

on chain

High

Manta

on chain

High

ZKFair

on chain

High

Blast

on chain

High

Linea

on chain

High

B2

on chain

High

Merlin

on chain

High

How to Configure Transaction Bot Monitoring?

After logging into ChainBot platform, go to the top right "Create Bot" -> "Transaction Monitor".

Field Descriptions

FieldDescriptionRequired

Name

Bot Monitor Name

Yes

Chain

Selected Chain

Yes

Contract

Selected Smart Contract Address

Yes

Function

Selected Smart Contract Method

Yes

Tags

Bot Monitor tags for easy searching

Yes

Condition Descriptions

ConditionSymbolDescription

From

==, in

From address sending the transaction, varies by chain

To

==, in

To address receiving the transaction

Value

>, >=, <, <=, ==, !=, in

Value of the transaction, default unit is wei, 1ETH == 1000000000000000000

methodId

==, in

MethodID of the transaction, must start with 0x followed by 4 bytes, e.g., 0x95d89b41

data

Can be empty

Entire string

Template Variable Descriptions

VariableDescription

$subscription.name

Subscription name, usually the same as Bot Monitor name

$chain.explore

Blockchain explorer prefix

$chain.network

Chain's chainId

$block.time

Timestamp of the block where the transaction occurred

$tx.hash

Transaction hash

$tx.height

Block height where the transaction occurred

$tx.nonce

Transaction nonce value

$tx.from

Transaction sender address

$tx.to

Transaction recipient address

$tx.value

Transaction ether value, should be $tx.value/1e18 if in ETH units

$tx.gas

Gas fee consumed by the transaction

$tx.gasPrice

Gas price of the transaction

$tx.input

Transaction input data

$tx.type

Transaction type

$tx.accessList

Supported for some transactions

$tx.chainId

ChainID of the transaction

$tx.maxFeePerGas

Available after ERC-1155

$tx.maxPriorityFeePerGas

Available after ERC-1155

$tx.r

R value of the transaction signature

$tx.s

S value of the transaction signature

$tx.v

V value of the transaction signature

$tx.method

Transaction method name

$tx.success

Transaction status (success or failure), supported only for Aptos

$tx.type_arguments

Transaction status (success or failure), supported only for Aptos

$tx.arguments

Transaction status (success or failure), supported only for Aptos

Default Alert Template

[ {$subscription.name} ]
From: {$tx.from}
To: {$tx.to}
Method: {$tx.method}
Explore: {$chain.explore}/tx/{$tx.hash}
Time: {$block.time}
Created By chainbot.io

Learn about Alert Notification Templates

Notification Message Example

[ Transaction Monitor ] Name: MIM Issuance Monitoring From: 0xfddfe525054efaad204600d00ca86adb1cc2ea8a To: 0x5f0dee98360d8200b20812e174d139a1a633edd2 Method: execTransaction(address,uint256,bytes,uint8,uint256,uint256,uint256,address,address,bytes) Explore: https://etherscan.io/tx/0x5a1a9f01fd3fad6fa3909bcdd284e8023eedf9797d94458a13bb6df929d80a1a Time: 2022-05-10 22:40:29 +0800 CST

Created By ChainBot.io

Transaction Bot Monitoring Case

Transaction Bot Case Study

Last updated