Skip to content
BellchainDocs

Watching wallets

With the Wallet node, Bellchain tells you when something comes in or goes out of a wallet: your own wallet as a guard, the wallet of a project or a large holder, or when you are waiting for a payment. Bellchain only reads public data of the blockchain for this. You enter the address, never a recovery phrase or a private key.

The node comes with Pro. Your active chains watch up to 10 wallets together on Pro, 50 on Trader and 100 on Community; each address counts once, also with several coins or in several chains.

Networks and coins

Section titled “Networks and coins”
Network Addresses Coin USDT USDC
Bitcoin bc1…, 1…, 3… BTC – –
Ethereum 0x… ETH yes yes
Base 0x… ETH – yes
Arbitrum 0x… ETH yes yes
BNB Chain 0x… BNB yes yes
Polygon 0x… POL yes yes
Solana 32 to 44 characters without 0x SOL yes yes

Base, Arbitrum, BNB Chain and Polygon use the same addresses as Ethereum. Choose the network the balance is on; Bellchain checks whether the address fits the network and says so under “Notes” if not.

How to set it up

Section titled “How to set it up”
  1. Drag the Wallet node from “Sources” onto the board.
  2. Choose Network and Coin and paste the Address.
  3. From amount sets from which movement it reports, counted in the chosen coin. With 0 it reports every movement, including dust of a few cents that strangers send to many wallets.
  4. Connect incoming or outgoing to an action such as Telegram.

Without a candle the chain reports right away: Bellchain asks for the balance every 10 seconds and computes the chain as soon as it changes. The alert usually arrives within 15 seconds after the network has confirmed the transfer; on Bitcoin that means with the next block, after 10 minutes on average. If the chain has a candle, it reports at the candle’s close, so after 5 minutes at the latest with 5-minute candles. Which pair the candle has does not matter for the wallet.

To try it out: activate the chain and then send a small transfer. Whatever came in before activating is not reported. After an alert the action rests for its cooldown (“At most every … hours”, 4 hours by default); to report every transfer, set it to 0.

Balance of a wallet in ETH with incoming and outgoingThe balance rises twice and falls twice; the small outflow of 0.05 ETH is below “From amount” and triggers nothing.Balance (ETH)01234incoming (from 0.1 ETH)outgoing (from 0.1 ETH)Oct 9Oct 10Oct 11Oct 12Oct 13Oct 14Oct 15Oct 16Oct 17
  • balance
Made-up values of a wallet on Ethereum over three weeks in hourly candles, with “From amount” 0.1 ETH. “Incoming” and “outgoing” are true at the first candle at which the new balance is certain, so at exactly one candle per movement. The node does not report the outflow of 0.05 ETH.

When the node reports

Section titled “When the node reports”
  • Bellchain asks for the balance every 10 seconds while an active chain watches the wallet; on Bitcoin as soon as there is a new block. Only confirmed transactions count.
  • The movement of a candle is the balance at its close minus the balance at its start; when the wallet is first observed, the first balance counts as the start. incoming and outgoing are true at the candle in which the balance changed, so at exactly one candle per movement. Without a candle a candle is one minute long, and the chain reports while the minute is still running.
  • Bellchain compares balances, not single transactions: if something comes in and goes out again within one candle, only the difference counts. Without a candle or with short candles you see more single movements.
  • The alert names the movement, such as “Wallet SOL movement: 0.001”.
  • On EVM networks and Solana, outgoing transfers cost a fee in the network’s coin. If you watch USDT, the fee does not count; if you watch the coin, it is part of the movement.
  • Movement outputs the amount by which the balance changed, Balance the current level; both fit into a message.

Using balance and movement

Section titled “Using balance and movement”

The shape of a pin shows what fits together: a square is a signal (true or false), a circle a number, a diamond a text. incoming and outgoing therefore go straight to an action’s Trigger. Balance and Movement are numbers; they need a node in between, depending on what you want:

  • The number in the text: connect Movement to input A and Balance to B of a Message template, its output to the action’s Message, and write something like +{{a}} SOL received, balance now {{b}} SOL. Without a template the alert names the movement by itself.
  • The number as a trigger: a Compare turns a number into a signal. Balance below 0.05 SOL reports when the wallet for fees is almost empty. Movement above 99 and below 101, joined with AND, reports a payment of exactly 100 USDT.

Replay

Section titled “Replay”

There is a history of balances only from the moment an active chain watches the wallet. Bellchain does not load older history, so a new wallet shows nothing in the replay at first, and the history grows every day. If asking fails for longer than 7 hours, the balance stays empty in between, and a movement during that time is not reported.

Who sees the address

Section titled “Who sees the address”

Bellchain’s server asks public services of each network for the balances. These services see the address and the address of the server, nothing about you or your account. Which services they are is in the privacy policy, section 7.

Version 2026.10.25.16 · Changelog