Source: https://cryptanio.com/wiki/monitor-multiple-crypto-wallets/
Language: en

# How to monitor multiple crypto wallets in one place

Bring public addresses from several wallets into Monitoring\, choose networks\, assets\, and transfer directions\, view combined events\, and receive the notifications you need\.

Updated: 2026-11-14

You can monitor several cryptocurrency wallets through their public addresses in Monitoring\: add the required addresses to Cryptanio projects\, select assets and transfer directions\, then view events in a shared list\. Funds stay in the wallets\; this monitoring does not require seed phrases or keys for signing transfers\.

Consider a business setup with a store address\, a separate reserve address\, and another wallet on a different network\. You want to see new receipts and outgoing transfers without checking every address separately in different applications\. This setup collects address events rather than moving wallets or funds into Cryptanio\.

## Make a list of addresses and networks {#make-a-list-of-addresses-and-networks}

List the public addresses you actually want to monitor\. Note the network\, purpose\, and required assets for each one\. Names such as “Store” and “Reserve” help you recognize entries\, but the network must still be selected separately\.

One wallet can use several addresses\. Connecting one public address does not automatically discover all other addresses in an HD wallet\, change addresses\, or all networks shown by the wallet application\. First define the specific set to monitor\. If a new address appears later\, check that it is connected too\.

Even the same address string on different networks does not combine their histories\. The difference between a network and an asset is explained in the [reference article](<https://cryptanio.com/wiki/network-and-token/>)\.

## 1\. Choose projects for different tasks {#1-choose-projects-for-different-tasks}

You need an account with management permissions and a project with an active Monitoring service\. If you do not have one yet\, start in “My services” and activate Monitoring\. Check that address capacity is available\; the dashboard shows the current limits\.

Several addresses serving one purpose are conveniently kept in one project\. For another store or personal transactions\, you can use a separate project with independent monitoring and notification rules\. You do not have to create a project for every wallet\.

## 2\. Add public addresses {#2-add-public-addresses}

Open Monitoring and the relevant project\. Click “Add addresses\.” On the “Manually” tab\, select the network\, paste the address\, and give it a clear name\. Do not paste a private key or recovery phrase into the address field\.

If addresses are already saved\, use the “Address book” tab in the same form and select the required entries\. They must be connected specifically to Monitoring for the relevant project\: storing them in the book alone does not start monitoring\. Repeat the connection for the other networks and addresses on your list\.

Before saving\, check the network availability message\. A mode in which live monitoring is unavailable does not track real transfers\. After adding an address\, check that it is active\, rather than merely saved or paused\.

## 3\. Choose assets and directions {#3-choose-assets-and-directions}

In “Use in project\,” set “Assets to count\.” For supported tokens\, the options are “One asset\,” “Selected assets\,” and “All detected assets\.” Their availability depends on the selected network\.

For one coin or token\, specify the required asset\. An empty field means the network\'s native coin\. For a set of tokens\, use their exact identifiers\, such as contract or mint\, in the format requested by the form\. A token\'s name and logo do not replace checking its identity\.

“All detected assets” refers to assets on the selected network within the available monitoring coverage\. It does not automatically connect every blockchain\, new wallet addresses\, or complete history\.

Select “Incoming” for receipts and “Outgoing” if you need sent transfers and the selected network supports them\. At least one direction must be enabled\. Set additional thresholds in the units specified by the form\: a minimum amount in base units requires accounting for the asset\'s precision\.

## 4\. View events together or separately {#4-view-events-together-or-separately}

In the main “Events” section\, the “All” tab shows available events from different projects\. To investigate a particular wallet\, select the project and use the network and address filters\. Also check the asset and event type\: incoming and outgoing transfers are different operations\.

For a disputed case\, save the [transaction identifier](<https://cryptanio.com/wiki/transaction-id-txid/>)\. It helps match the entry to the network explorer\. Transfer discovery and [confirmation](<https://cryptanio.com/wiki/transaction-confirmations/>) can happen at different stages\; do not treat every new entry as a final result\.

## 5\. Configure project notifications {#5-configure-project-notifications}

In the project\'s “Notifications\,” check whether account settings are inherited\. You can use shared channels or the project\'s own routes\. A connected messenger does not by itself determine which project events are sent there\.

Select the required event types\. The “Confirmed payments” policy does not automatically include confirmed outgoing transfers\: they have a separate event type\. For messages in a work channel\, use the [Slack guide](<https://cryptanio.com/wiki/crypto-transaction-notifications-slack/>)\; for personal notifications\, use the [Telegram guide](<https://cryptanio.com/wiki/telegram-crypto-transaction-notifications/>)\.

## How to check that monitoring works {#how-to-check-that-monitoring-works}

After setup\, wait for a new matching transaction and find it in the correct project\. If you expect a notification\, check its entry in “Deliveries\.” The connection test button tests message delivery\; it does not create a transaction or prove that address monitoring works\.

If an event is missing\, check the address\, network\, asset\, direction\, pause\, and service status\. A complete archive of transfers before connection is not promised\. When a new address appears or your needs change\, revisit the monitoring list\: an absent event does not by itself prove that a wallet holds no funds\.

Tags: [Monitoring](https://cryptanio.com/wiki/tag/monitoring/)

## Related articles

- [How networks and tokens differ](https://cryptanio.com/wiki/network-and-token/)
- [What is a TXID and where can you find a transaction ID\?](https://cryptanio.com/wiki/transaction-id-txid/)
- [What transaction confirmations mean](https://cryptanio.com/wiki/transaction-confirmations/)