Compare each scheduled token release with the same token’s price and trading activity around the release date. A vesting unlock makes tokens available under a schedule; it does not prove that anyone sold them, so look for a repeated timing pattern and check what else was happening in the market.
What does a vesting unlock schedule tell me?
A vesting schedule describes when restricted tokens become available to their recipients. It may specify a cliff, when nothing is released until a set date, followed by a linear stream or regular tranches. A cliff can create one large release; a recurring tranche creates repeated dates to compare with the chart.
Start with the project’s tokenomics or vesting announcement, then look for confirmation in the relevant contract or transaction history. OpenZeppelin’s VestingWallet documentation describes one common implementation: tokens vest according to a schedule, and a beneficiary can release the amount that has vested. Projects can use different contracts and rules, so don’t assume that every schedule is implemented the same way.
Record the release date, amount, recipient group, and whether the figure is a one-time tranche or part of a continuing stream. Check whether the stated amount is a share of the total supply or the circulating supply—the amount already available to the market. A release of 2% of circulating supply may matter more than the same number expressed as a small share of total supply.
How do I line up unlock dates with chart selloffs?
Put the scheduled dates beside the price history, then compare price and activity across consistent time windows. For example, inspect the seven days before and after each monthly unlock; use the same window for every date so the comparison is meaningful. A BSC charting tool such as PooCoin can help you inspect a token’s chart while you check the schedule against its history.
For each event, note the price change, trading volume, and—where available—liquidity. Volume is the amount traded; liquidity is how much can be traded without moving the price sharply. On a decentralised exchange pool, a modest sell can move a thinly traded token more than a larger sell would move a deep market.
Look for a pattern across several releases, not one striking candle. If price repeatedly weakens just before or just after the same monthly date, that is a clue to investigate. It is not proof that recipients sold: traders may have anticipated the release, the wider market may have fallen, or another project event may have coincided with it.
What comparison makes the pattern more convincing?
Compare each event with both the token’s own recent trend and the wider market over the same dates. If the token falls 12% while BNB and similar assets are broadly flat, the move deserves closer attention than a 12% fall during a market-wide selloff. Also compare the token’s price and volume on non-unlock weeks; that gives you a baseline for its usual volatility.
Illustrative example: A project releases 3 million tokens on the 15th of each month, equal to 1.5% of circulating supply at the first release. Before the next date, check whether the prior month’s price began falling in the same window, whether trading volume rose, and whether the market benchmark was stable. If the same pattern appears across three or four releases, while comparable non-unlock weeks are calmer, recurring supply pressure becomes a stronger explanation—but still not a certainty.
Keep a small event table with the date, amount, percentage of circulating supply, seven-day price move before and after, volume change, and market benchmark move. If the circulating supply changes between events, recalculate the percentage each time; a fixed token amount can become a smaller share as supply grows.
What can make an apparent pattern misleading?
The key edge case is that an unlock, a transfer, and a sale are different events. Tokens becoming transferable may move from a vesting contract to a recipient wallet without reaching a trading pool. Check the contract and transaction trail where possible, but treat wallet movements as evidence of transfer, not proof of a market sale.
Schedules can also be estimates, amended, or implemented with different timing rules. Confirm dates and amounts from project disclosures and on-chain records when available. If the schedule cannot be verified, mark it as unconfirmed rather than treating chart timing as confirmation.
Use repeated timing, relative performance, and evidence of actual selling together; no single chart dip establishes the cause.