An alert may be triggered by a large token transfer to an address that is labeled as belonging to an exchange. If the price is already going down, the transfer could be a whale sale. Upon looking at the transaction details, you can see that tokens were sent to an address that your data provider believes is associated with an exchange. It does not confirm that they were sold.
A token deposit or contract call from a wallet that has been quiet for months can slip without an alert. A notification can trigger before any tokens move by a scheduled unlock.
Whale Transfer
Although the dollar amounts are often the most noticeable, the transaction hash is more useful. On chains like Ethereum, you can look up the transaction hash using a block explorer. You can see which token was sent, how much, and to/from which addresses. These are logs that contracts emit during execution. This can be useful if you want to understand what a whale alert refers to. It can be important when multiple contracts have been interacted with, or two tokens share the same ticker symbol.
Some projects publish their treasury address in their disclosures. You can look up the label and know it relates to the project. However, consistent patterns may lead analysts to identify exchange labels. An example of this is funds consistently being sent to the same place from an address. This can sometimes appear in two different alerts due to both services getting the label from the same data provider.
A whale alert may include two addresses and a transaction hash below the dollar amount. Webopedia’s guides explain both to wallet addresses and Bitcoin transactions. The addresses show where the money came from and where it went. The hash is unique to the transaction. Using the hash in a Bitcoin explorer will show the transaction details.
Exchange Inflows
Users may hold tokens in an exchange account or use them as collateral if the exchange allows it. If the account holder makes a spot trade, the centralized exchange will typically match it on its own books. The deposit has its records in the on-chain transaction. Any subsequent spot trades appear in the exchange’s own records.
The addresses associated with a transfer may both be from the same exchange. Glassnode’s exchange data methodology describes how internal transfers can initially register as large inflows or outflows. When a customer deposits funds and the venue transfers them to its main wallet, the system may trigger two transfer alerts. Adding the two together would mean you are double-counting the funds.
When looking at a spike, it can be easier to compare with recent inflows for the same asset/venue in the same timeframe. Gross inflows show how much users added. Net flow shows how much was deposited minus withdrawals. Large deposits may be accompanied by small net inflows due to high withdrawals. Numerous substantial deposits from seemingly unrelated wallets provide additional context for the alert if spot trading surges on the same exchange subsequently. The public trade feed can show the increase in volume, but it cannot provide readers with information on whether the depositors sold.
Unlock Alerts
On a scheduled vesting date, an unlock can go out before any tokens move. A cliff unlock makes a block of tokens available at once, while linear releases smaller amounts over time. Recipients may still need to claim their tokens, depending on release setup.
The unlock may not be significant compared to the circulating supply but can be large compared to bids on an exchange. The alert will show the value of the full amount based on the current price. If a large number of recipients start sending funds to trading venues, the order book will show how many tokens buyers are bidding for at or near the current price.
Project disclosures may show who is due to receive the tokens and whether the release schedule has changed. If the distribution is visible on-chain, you can get more evidence of what happened on the day of release. The tokens may still be in the recipient’s wallet, or a further transfer may show they have gone to an exchange.
Unusual Wallet Activity
If a wallet has been inactive for a long time, it may stand out when it starts moving tokens. A bridge contract can appear like an exit in a feed covering only one network. The destination contract and the receiving chain show where the assets went.
If most of the wallet’s activity is basic transfers, its approval can stand out. A token approval can give a smart contract permission to spend tokens from the wallet later. A swap shows that assets were exchanged. If the contract spends the tokens, its address and the wallet’s history can show whether they have interacted before.
When AI crypto signals flag accumulation, the wallet addresses, time frame, and transaction links show what the tool detected. A short summary can mistake movement of tokens between wallets for purchases. A new summary may include an old transfer; the timestamp shows when it took place.
Smaller Feed
A single dollar threshold can fill a feed with routine transfers in liquid assets. This may miss any meaningful changes in smaller markets. Having a watchlist for specific tokens/venues/treasury wallets from disclosures can give context to the size. A calendar reminder flags an upcoming unlock. A separate alert can show when the tokens reach the recipient.
Having a short alert history can show which rules are useful. A transfer that repeatedly turns out to be a custody sweep may belong in a digest. A rule highlighting that tokens have moved from a known vesting wallet may be worth keeping. Including the transaction hash and what happened can make it easier to decide in a busy week. You may only remember the largest dollar amounts.
