Skip to main content

Whale Wallet Monitor

Track a wallet address for balance changes, large transfers, and contract interactions across EVM and Cosmos SDK chains.

Why teams use this monitor

Wallet monitoring is usually the fastest path from “we have a blockchain integration” to “we need actionable alerts when money moves.”

  • Treasury and finance operations
  • Exchange and bridge flow monitoring
  • Teams tracking a founder, whale, or operational hot wallet

Quick start in 5 minutes

  1. Start with one address that matters operationally: treasury, exchange wallet, or your main payout wallet.
  2. Set a balance change threshold high enough to ignore routine noise.
  3. Add a minimum transaction value only after you know what “normal” movement looks like.

Configuration notes

FieldWhat to know
chainId / chainIdStringUse chainId for EVM and chainIdString for Cosmos SDK chains. The form enforces exactly one of them.
restApiUrlCosmos wallets need a REST endpoint for account and tx data. Do not leave it blank if you choose a Cosmos chain.
balanceChangeThresholdPercentSmall wallets need tighter thresholds; treasury wallets usually need larger ones to avoid noise.
minTransactionValueEthDespite the field name, use it as a practical “large movement” floor for the selected chain.

Recommended thresholds and defaults

  • Treasury wallets often start with 3-5% balance-change alerts.
  • Hot wallets with many routine transfers usually need a minimum transaction value to stay actionable.
  • If you enable ERC20 tracking, expect more noise until you narrow the watch to a specific operational wallet.

Ready-made examples

Treasury wallet monitor

Watch your main operational wallet for meaningful balance shifts.

Setup time: 3 min

Best for

DAOs, treasuries, and projects with a known main wallet

  • Ethereum wallet
  • 5% balance-change alert
  • 100 ETH large-tx floor
{
  "name": "Treasury wallet monitor",
  "address": "0x742d35Cc6634C0532925a3b844Bc9e7595f2bD18",
  "chainId": 1,
  "rpcUrl": "https://eth.llamarpc.com",
  "label": "Treasury",
  "balanceChangeThresholdPercent": 5,
  "minTransactionValueEth": 100,
  "trackErc20Transfers": true,
  "checkIntervalSeconds": 60
}

Exchange outflow watch

Detect large movements from a known exchange wallet.

Setup time: 3 min

Best for

Market intel and exchange liquidity monitoring

  • Binance hot wallet
  • 2% balance-change alert
  • 500 ETH large-tx floor
{
  "name": "Exchange outflow watch",
  "address": "0x28C6c06298d514Db089934071355E5743bf21d60",
  "chainId": 1,
  "rpcUrl": "https://eth.llamarpc.com",
  "label": "Exchange flow",
  "balanceChangeThresholdPercent": 2,
  "minTransactionValueEth": 500,
  "trackErc20Transfers": false,
  "checkIntervalSeconds": 60
}

Cosmos ops wallet

Use a Cosmos-safe preset for a bech32 operational wallet.

Setup time: 4 min

Best for

Teams receiving funds or making payouts on Cosmos SDK chains

  • Cosmos Hub
  • REST + RPC configured
  • 4% balance-change alert
{
  "name": "Cosmos ops wallet",
  "address": "cosmos1skjwj5whet0l0d9z4rj8e0v9n7p2m4u4s0s9s7",
  "chainIdString": "cosmoshub-4",
  "rpcUrl": "https://rpc.cosmos.network",
  "restApiUrl": "https://rest.cosmos.directory/cosmoshub",
  "label": "Ops wallet",
  "balanceChangeThresholdPercent": 4,
  "trackErc20Transfers": false,
  "checkIntervalSeconds": 120
}

Alert example

Large wallet movement

Wallet alert: treasury wallet sent a large transaction.
Direction: outgoing
Value: 750 ETH
Suggested action: confirm whether this transfer was scheduled and review the recipient contract or address.

Troubleshooting

An EVM wallet validates but never reports activity.

Check whether you selected the right chain. The same address can exist on multiple EVM networks with unrelated activity.

Cosmos address looks valid but create fails.

Verify the bech32 prefix matches the chain you selected and that the REST endpoint is reachable.

You receive too many low-value alerts.

Raise balanceChangeThresholdPercent or add minTransactionValueEth before disabling the monitor.

Next steps