Watching an Address You Care About
6 min read · Verified September 2026
A wallet transaction alert notifies you when an address you specify sends or receives funds on-chain. It works on public blockchain data, so it needs only the address, never a key. It watches addresses you already know. It does not discover addresses or identify unknown holders. Pro and Pro+ feature.
Blockchains publish every transaction. Anyone can read them, nobody needs permission, and the data is the same whether you look at it through a block explorer or through an app. What is hard is not access. It is attention. Nobody is going to refresh Etherscan every morning to check whether a particular address has moved, and the one morning it matters is the one you skipped.
A wallet transaction alert is the fix for that specific problem. You give it an address, and it tells you when funds move in or out of that address. That is the entire feature, and its usefulness comes from how narrow it is.
What are these alerts actually for?
Three uses account for almost everything people do with them, and all three share a shape: you already know the address, and you care about it for a concrete reason.
Your own cold storage. This is the most valuable and the most under-used. A hardware wallet holding a long-term position is, by design, something you touch rarely, which means an unauthorised movement could sit unnoticed for months. An alert on that address turns a passive holding into a monitored one. If funds ever leave and it was not you, you know within minutes instead of at your next quarterly check. That is not a theoretical benefit for anyone who has ever approved a contract interaction they did not fully understand. Tracking a hardware wallet covers adding the address as a watched position, and this alert sits naturally on top of it.
The same logic applies to a shared or multisig treasury address, or a wallet you keep for one purpose and rarely open.
A treasury or protocol address you have exposure to. If you hold a token, the project's treasury and its designated addresses are public, and their movements are material to you. A treasury sending a large balance to an exchange deposit address is information that reaches the market eventually. It reaches you immediately if you are watching. The same goes for a foundation address, a grants multisig, or a designated market-maker wallet where the project has published which address is which.
A vesting or unlock contract. Token unlocks are scheduled events, and the schedule is usually public, but the schedule and the actual movement are different things. Tokens frequently sit in the vesting contract for weeks past their cliff, then move all at once. An alert on the contract address tells you the moment supply actually starts travelling, which is the event that matters rather than the date on the calendar. Supply and unlocks covers reading those schedules; this alert covers the gap between the schedule and reality.
Watching an address needs the address only, never a key or a signature.
How do these alerts work against public chain data?
There is no privileged access involved. An indexer reads confirmed blocks on each supported chain, matches transactions against the addresses users have asked to watch, and dispatches a notification. The same information is visible to anyone with a browser. What the alert provides is monitoring, running continuously, without you doing anything.
Two consequences follow from that architecture, and both are worth understanding.
The first is that you only ever supply a public address. Not a key, not a seed phrase, not a signature, not a connected wallet session. The address is the string you would put on an invoice. This makes address monitoring the lowest-risk thing you can do with a crypto app, because there is nothing to steal. If any product ever asks for a seed phrase to set up monitoring, that is the attack itself, which never share your seed phrase covers in full.
The second is that alerts fire on confirmation, not on broadcast. A transaction sitting in the mempool can be replaced or dropped, so waiting a block or two avoids notifying you about something that never happened. On fast chains this is a matter of seconds. On Bitcoin it is longer, and it should be.
Address entry has a privacy dimension worth naming honestly. Watching an address associates that address with your account, and on chains where address activity is easily clustered, watching your own addresses is one more place they exist together. This is a small consideration next to the benefit for most people, but it is a real one, and the wallet privacy tradeoff works through it properly. What a tracker can see covers the equivalent question for portfolio connections.
What can't these alerts tell you?
This is the part that gets oversold elsewhere, so here it is plainly.
They do not discover addresses. The feature watches what you enter. There is no search across the chain for large holders, no ranking of balances, no list of significant addresses to subscribe to. If you do not already know the address, this will not find it.
They do not identify anybody. An address is a string. Attaching a name to it requires outside information: a project's own published documentation, an exchange's disclosed deposit addresses, or public labelling work done by someone else. The alert reports that address 0xabc… moved 4,000 ETH. Whose ETH that was, and why it moved, is a research question the alert does not answer and does not pretend to.
They do not interpret intent. Funds moving to an exchange deposit address is the classic case. It is often read as an intent to sell, and sometimes that is right, and sometimes the same movement is a transfer to an OTC desk, a collateral posting, an internal reshuffle between custody providers, or a market maker rebalancing inventory. The alert reports the movement. Everything after that is inference, and confident-sounding inference about single transactions is wrong a great deal of the time.
They do not see inside contracts. A position held inside a lending protocol, a liquidity pool or a staking contract is not sitting at your address, so movements within it may not produce an address-level alert. Tracking a multichain identity covers how holdings spread across contracts and chains appear at the address level.
Wallet transaction alerts run on Pro and Pro+, along with volume, market cap and pump alerts. Simple price and percentage alerts are on the free tier.
If you take one thing from this, set an alert on your own cold storage address before you set one on anybody else's. It is the use with the clearest payoff, it takes about twenty seconds, and it converts the largest single position most people hold from something they hope is fine into something they would hear about within minutes if it were not.
Common questions
No, and you should never enter one anywhere. Watching an address requires only the public address, which is the string you would give someone to receive funds. The alert reads the same public ledger a block explorer reads. Anything asking for a seed phrase to set up monitoring is an attack.
No. These alerts watch addresses you have entered yourself. There is no discovery step, no ranking of holders and no identification of who owns what. If you do not already know an address, this feature will not find it for you.
No. Reading public chain data leaves no trace on the chain, and the address owner has no way to know an alert exists. The privacy question runs the other way: entering an address associates it with your account, so use your own judgement about which addresses you enter.
Within roughly a block or two of confirmation on most chains, so seconds to a few minutes depending on the network. Faster chains deliver faster. An alert waits for confirmation rather than firing on a pending transaction, because pending transactions can be dropped or replaced.
It works on the chains covered by the app's on-chain support, which spans 15 or more networks. An address on an unsupported chain, or a bridged position sitting inside a protocol contract rather than at your address, will not produce alerts.
Portfolio tracking tells you what a balance is. A transaction alert tells you the moment it changed, which is the part that matters for cold storage, for a treasury you have exposure to, or for a vesting contract you want to know about before the market does.
Wallet transaction alerts come with Pro at $8.99 a month, alongside volume, market cap and pump alerts.
Keep reading
Tracking a Hardware Wallet Without Exposing Anything
Watch the public address instead of connecting the device. What an address reveals, whether to share a Bitcoin xpub, and why no tracker needs a seed.
The Privacy You Give Up When You Use a Public Address
Your address publishes your balance and full history to anyone, permanently. How addresses get linked to identities, and which mitigations work.
What a Portfolio Tracker Can Actually See
Balances and trade history, yes. Private keys, seed phrases and moving funds, no. What the app, the company and the public can each actually see.
Nobody Legitimate Will Ever Ask for Your Seed Phrase
A seed phrase is the wallet, not a password for it. Why no real app or agent needs one, the scripts scammers use, and what to do if you shared it.
Circulating Supply, Unlocks, and the Chart You Can't See
Vesting schedules create future supply no price chart shows. Where to find an unlock schedule, cliff versus linear vesting, and why dates are knowable.
One Address, A Dozen Chains, One Number You Don't Trust
Your EVM address exists on every EVM chain whether you used it or not. How to decide which chains to watch, and why a tracker double-counts or misses one.
What an Ethereum Address Actually Tells Someone
An Ethereum address is one public identity reused across dozens of chains. What a tracker reads, what approvals it cannot see, and where the same 0x lies.
Why a Portfolio App Needs Its Own Lock
A device passcode protects a locked phone. Most exposure happens on an unlocked one. What an app lock adds, and what it cannot possibly do.