Large Transfer Alerts with the Transaction Value Monitor

Get told when a wallet sends or receives more than an amount you set, in the chain's native token or in one ERC-20 token.

A balance alert tells you a wallet is lower than it should be. A transaction value alert tells you why, the moment it happens: which transfer moved the money, how much, and to whom. That is the signal a treasury team, an exchange operations desk or a security lead wants when a large amount leaves a wallet.

The Transaction Value Monitor watches one address on one chain and alerts when a transaction from or to it is above, or below, a threshold you choose.

How it works

  1. Every block is read. Chainitor reads each new block once and selects the transactions sent from or to your address, in the direction you chose.
  2. The value is compared. A transaction's native value, in ETH, BNB or POL, is compared with your threshold using greater than or less than.
  3. Optionally, one token too. With token transfers on, Chainitor also reads that token's Transfer events to or from the address and compares the amount in the token's own units, using its decimals().
  4. You are alerted at your next check. At each check (every minute at the fastest on Pro), any match turns the monitor critical and sends an alert with the amount, the direction and the transaction hash. A check with no new matches sends a recovery notice.

What you configure

  • Chain: Ethereum, Polygon, Arbitrum, Optimism, BNB Chain, Base, Robinhood Chain, or the Ethereum Sepolia, Polygon Amoy, BSC testnet, Arbitrum Sepolia, Optimism Sepolia and Base Sepolia testnets.
  • Address: the wallet or contract to watch.
  • Direction: outgoing, incoming, or both.
  • Threshold and condition: an amount, and whether a transfer must be greater than or less than it.
  • Token transfers (optional): the contract address of one ERC-20 token to watch as well.
  • Check interval and alert channels: email, Slack, Telegram, PagerDuty and webhook are on every plan.

Example configurations

Treasury outflow above 50 ETH

Monitor type
Transaction value
Chain
Ethereum
Address
0x3333333333333333333333333333333333333333 (treasury, placeholder)
Direction
From address (outgoing)
Condition
Greater than 50
Alert channels
Slack #treasury and email to finance

Any transaction that sends more than 50 ETH out of the treasury alerts with the amount and the transaction hash; the sender and recipient are kept in the monitor's history.

Large USDC deposits into an exchange hot wallet

Monitor type
Transaction value
Chain
Base
Address
0x4444444444444444444444444444444444444444 (hot wallet, placeholder)
Direction
To address (incoming)
Condition
Greater than 250000
Include token transfers
Yes: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC on Base)

USDC transfers into the wallet are compared in USDC, using the token's own decimals, so 250000 means 250,000 USDC. The same threshold also applies to native ETH sent to the wallet, where 250000 means 250,000 ETH, so in practice this monitor only alerts on USDC. To catch large ETH deposits as well, add a second monitor with an ETH-sized threshold, such as 100.

Who uses large transfer alerts

  • Treasury and finance teams: a second pair of eyes on outflows above an approval limit.
  • Security teams: an early signal that a hot wallet is being drained, before the balance alert fires.
  • Exchanges and payment processors: large deposits that should be reviewed or credited by hand.
  • Researchers and traders: a whale wallet moving funds. Watching an address needs no permission from its owner.

Limits worth knowing

  • Native value is the value of the transaction itself. ETH a contract forwards during a call (an internal transfer) is not counted.
  • One threshold applies to both the native value and the token amount, so set it with the token in mind when token transfers are on.
  • Amounts are in token units, not US dollars.
  • Native value is compared whether or not the transaction succeeded: a reverted transaction that carried more than the threshold still matches, even though no ETH moved. Pair it with a failed transaction monitor on the same address to see which of those transfers reverted.
  • Less than matches every transaction below the amount, including zero-value contract calls, so it is mainly useful on addresses that only receive plain transfers.

Frequently asked questions

What does the transaction value monitor compare?

The native value of each transaction sent from or to your address, in the chain's gas token (ETH, BNB or POL), against a threshold with greater than or less than. If you add a token, that token's transfers to or from the address are compared too, in the token's own units.

Can it alert on ERC-20 transfers, such as USDC or USDT?

Yes. Turn on token transfers and give the token contract address. Chainitor reads that token's Transfer events, so a transfer counts even when it was made through another contract, such as a router or a multisig. One monitor watches one token.

Does it see ETH sent by a contract, for example from a Safe?

The native check reads the value of the transaction itself. ETH moved by a contract during a transaction, such as a Safe executing a payment, is an internal transfer and is not included. For tokens this does not apply: token transfers are read from the token's events.

Will I get one alert per large transfer?

The first matching transfer turns the monitor critical and sends an alert with the amount and transaction hash. Further matches while it stays critical do not repeat the alert; the first check with no new matches sends a recovery notice, and the next match alerts again.

Which plan includes transaction value monitors?

The Pro plan and above. Transaction value monitors read every block of their chain, so they are not part of the Starter plan.

Related monitors and guides

Know when large amounts move

Set up a large transfer alert on any address in a couple of minutes. Transaction value monitors are part of the Pro plan.

Start monitoring free

7-day free trial ā€¢ No immediate charge