Track Token Unlocks and Vesting with Dune Dashboards
Token unlock tracking on Dune is the most powerful way to stay ahead of supply dilution events in crypto. Whether you're a trader, investor, or protocol analyst, understanding when large amounts of tokens become liquid directly affects your portfolio risk management. Dune's community-built dashboards transform raw on-chain data into actionable insights about vesting schedules, cliff releases, and linear unlocks.
In this guide, you'll learn exactly how to build your own token unlock dashboard, from selecting the right tables to visualizing daily release rates. We'll walk through real examples using major protocols, compare different vesting mechanisms, and show you how to automate alerts so you never miss a critical unlock event. By the end, you'll have a production-ready framework for monitoring any ERC-20 token's supply schedule.
- Token unlock tracking Dune dashboards rely on querying ERC-20 transfer events from known vesting contract addresses.
- Cliff unlocks release a large chunk at once; linear vesting releases tokens continuously over time.
- Always verify vesting contract addresses and decode custom events for accuracy.
- Dune's Spellbook provides standardized tables for popular tokens like UNI, ARB, and AXS, simplifying queries.
- Combine unlock data with token price feeds to estimate the dollar value of incoming sell pressure.
- Building your own dashboard gives you control over assumptions, parameters, and alert triggers.
Why Token Unlocks Matter for Trading and Risk Management
Understanding token unlock events is critical because they directly affect supply dynamics and price. When large amounts of tokens are released from vesting contracts – especially during cliff unlocks – the market often anticipates sell pressure. For example, after Arbitrum's March 2023 unlock of over 1 billion ARB tokens, the price experienced significant volatility. By using Dune dashboards to track these events, you can position yourself ahead of known dilution windows.
Moreover, many retail investors overlook the gradual linear vesting that leads to daily supply inflation. A well-built Dune dashboard reveals not just the next cliff but the continuous drip of tokens entering circulation. This allows you to compare a project's scheduled inflation rate against its organic demand, giving you an edge in fundamental analysis.
"The best traders don't just watch price; they watch supply. Token unlock tracking Dune dashboards are the microscope for supply-side analysis." — Anonymous Dune power user
Key Data Points Every Vesting Dashboard Must Include
To build a useful token unlock tracking Dune dashboard, you need at least these data points:
- Vesting contract addresses – usually found in project documentation or on Etherscan
- Transfer events from these contracts to beneficiaries (e.g., team, investors, treasury)
- Timestamp of each transfer to determine unlock date
- Token amount in human-readable units (adjust for decimals)
- Cumulative unlocked supply over time
- Percentage of total supply unlocked to gauge dilution severity
Optional but powerful additions: token price (from Dune's price feeds or Oracle tables) to estimate USD value of unlocks, and label data for beneficiary categories (team vs. community).
Essential Dune Tables and Spellbooks for Unlock Data
Dune's architecture provides several entry points for token unlock tracking. The most fundamental table is erc20_ethereum.evt_Transfer, which logs every ERC-20 transfer. For tokens with dedicated Spellbook models, like arbitrum.ARB_evt_Transfer, you can query directly. However, most unlock tracking requires joining multiple tables.
Key resources include:
erc20_ethereum.evt_Transfer– raw transfer events across all tokens- Community-curated Dune labels – help identify known vesting contract addresses
- Spellbook tables for major tokens – e.g.,
uniswap_v3.UNI_evt_Transfer prices.usd– minute-level price feeds to value unlocks
For custom tokens, you'll need to manually add the vesting contract address. Dune's community labels also provide entity tags for known team/investor wallets.
Step-by-Step: Building a Basic Token Unlock Dashboard
Let's walk through creating a simple Dune dashboard for tracking UNI unlocks. Follow these steps in Dune's query editor:
- Identify vesting contracts: For UNI, the team vesting contract is
0x... (example)– verify on Etherscan. - Write a base query:
SELECT date_trunc('day', evt_block_time) AS unlock_date, SUM(value / 1e18) AS amount_unlocked FROM erc20_ethereum.evt_Transfer WHERE contract_address = '0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984' AND "from" = '0x...' -- vesting contract address GROUP BY 1 ORDER BY 1 - Create a cumulative sum: Use
SUM(amount_unlocked) OVER (ORDER BY unlock_date) AS cumulative - Join price data:
LEFT JOIN prices.usd ON symbol = 'UNI' AND prices.minute = unlock_dateto get USD value. - Visualize: In Dune's dashboard editor, add a bar chart for daily unlock amount and a line for cumulative.
- Add a table showing upcoming unlocks (next 30 days) for quick reference.
- Schedule refresh: Set to daily or hourly under dashboard settings.
This basic dashboard gives you a clear view of dilution pressure.
Comparing Cliff Unlocks vs. Linear Vesting in Your Charts
Not all unlocks are equal. Cliff unlocks release a large batch of tokens at a single point in time (e.g., after a 12-month lockup). Linear vesting releases tokens continuously over a period (e.g., 1/365 of total each day). Your Dune dashboard should make this distinction visually.
For linear vesting contracts, you'll see daily transfers of roughly equal amounts. For cliff unlocks, you'll observe a single massive transfer on a specific date. Some contracts, like Axie Infinity's AXS, combine both: a cliff after the lockup period followed by linear vesting. To model this accurately, you may need to examine multiple vesting contract addresses or parse the vesting contract's own events (e.g., VestingCreated or TokensReleased).
Dune's call_evt tables can decode custom events from vesting contracts if the ABI is known. This is more advanced but allows precise tracking of scheduled vs. actual unlocks.
Multi-Protocol Comparison Table: Uniswap, Arbitrum, Axie Infinity
| Protocol | Vesting Mechanism | Cliff Duration | Linear Period | Key Contract Address |
|---|---|---|---|---|
| Uniswap (UNI) | 4-year linear with 1-year cliff | 12 months | 36 months | 0x... (team vesting) |
| Arbitrum (ARB) | 4-year linear with no cliff | None | 48 months | 0x... (DAO treasury) |
| Axie Infinity (AXS) | 2-year linear with 1-year cliff | 12 months | 24 months | 0x... (staking rewards) |
This table illustrates how different schedules affect supply inflow. Notice that Arbitrum's lack of cliff means daily unlocks from day one, while UNI and AXS have a large cliff event followed by steady releases. When building your dashboard, categorize each vesting stream separately and then aggregate to see total dilution. Dune makes this easy with UNION queries across multiple contract addresses.
Advanced: Tracking Multiple Vesting Contracts and Aggregating Supply
Most real-world projects have multiple vesting contracts: team, investors, advisors, treasury, and staking rewards. To get a complete picture of token unlock tracking Dune dashboards must aggregate all sources. The approach:
- Compile a master list of vesting contract addresses from project docs, GitHub, or Dune's label repository.
- Write a CTE (Common Table Expression) that unions all transfer events from these contracts.
- Group by date and beneficiary category (if labels available).
- Calculate total unlocked and remaining locked supply using total supply (from
erc20_ethereum.evt_Transferwhereto= null or usetotal_supplytable).
For example, to track ARB unlocks across team, investors, and ecosystem fund, you might use three distinct contract addresses. Dune's parameterized queries let you switch between token symbols dynamically. This advanced setup provides a holistic view of supply inflation and helps identify when a project's tokenomics deviate from expectations.
Automating Alerts and Sharing Your Dune Dashboard
Dune supports scheduled refreshes and webhook notifications, but for truly automated alerts you can combine Dune with external tools. One approach: use Dune's API (available on Premium plans) to fetch dashboard data and trigger actions via Zapier or a custom bot. For example, you can set a threshold on daily unlock size (e.g., >$1M USD) and receive a Telegram alert.
Another method: embed your Dune chart in a Notion page or a personal website to monitor multiple dashboards at once. Dune also allows sharing dashboards via public link – many community members publish token unlock dashboards for popular tokens. By forking and modifying these, you skip the initial setup but still customize for your needs.
To share your token unlock tracking Dune dashboard, click "Share" and copy the public URL. You can also use the "Make a Copy" feature to let others iterate on your work.
Common Mistakes When Building Token Unlock Dashboards
Even experienced analysts make errors. Avoid these pitfalls:
- Using only transfer events without verifying the contract – some vesting contracts release tokens to a distribution contract, which then distributes; you may miss the true unlock date.
- Not accounting for token decimals – for example, USDC has 6 decimals, while most tokens have 18. Forgetting to divide by 1e6 or 1e18 leads to absurd numbers.
- Mixing different types of unlocks – cliff events and linear releases should be separate series on your chart, not aggregated into one.
- Ignoring the 'from' address – sometimes the vesting contract sends tokens to an intermediate wallet; you need to trace the full chain.
- Assuming all unlocks are equal – some tokens have transfer restrictions (e.g., locked for a period even after transfer). Check the token contract for any transfer blacklist or time lock.
Always cross-reference your Dune results with official tokenomics documentation or dashboards from trusted creators like @hildobby or @ilemi.
Real-World Analysis: How Unlock Events Impact Price (Case Studies)
While I won't share current prices, historical patterns show correlation. For instance, Axie Infinity's AXS experienced a notable price correction in the weeks following its cliff unlocks in 2021-2022. By monitoring Dune dashboards, traders could anticipate these events. Similarly, Arbitrum's early unlock schedule led to consistent sell pressure as daily linear releases entered the market.
When using Dune for analysis, look for: (1) the ratio of unlocked supply to 24h trading volume – if unlocks are larger than volume, selling pressure is high; (2) the concentration of unlocks among top addresses – if a single entity receives a large unlock, the risk is concentrated; (3) the trend in unlock size over time – accelerating unlocks suggest higher future dilution. These metrics transform raw data into actionable insights.
"A good dashboard doesn't just show data – it tells a story about supply risk."
Step-by-step
- Navigate to Dune.com, create an account, and open the query editor.
- Locate the vesting contract address for your target token from official documentation or Etherscan.
- Write a SQL query selecting from `erc20_ethereum.evt_Transfer` filtering by the contract address and `from` = vesting contract.
- Use `date_trunc('day', evt_block_time)` and `SUM(value / POWER(10, decimals))` to get daily unlock amounts.
- Add a cumulative sum with `SUM(amount) OVER (ORDER BY day)` to track total unlocked over time.
- Join with `prices.usd` table to estimate the USD value of each unlock.
- Create visualizations: bar chart for daily unlocks, line chart for cumulative, and a table for upcoming unlocks.
- Share the dashboard publicly and set a scheduled refresh interval (e.g., daily) under dashboard settings.
Common mistakes to avoid
- Assuming all token transfers from vesting contracts represent liquid supply immediately available on exchanges.
- Forgetting to adjust for token decimals (e.g., using raw values without dividing by 1e18 for most ERC-20 tokens).
- Using a single vesting contract address when the project has multiple (e.g., separate contracts for team, investors, treasury).
- Not filtering out internal transfers or rebalancing transactions that do not represent actual unlocks.
- Over-relying on a community dashboard without verifying its data sources and assumptions.
- Ignoring time zone differences when interpreting unlock dates – Dune uses UTC so midnight unlocks might appear on the wrong day locally.
Frequently asked questions
How do I find the vesting contract address for a token on Dune?
Check the project's official documentation, token distribution lists, or Etherscan's token holders page. Community-curated Dune labels can also help identify known vesting contracts.
What Dune tables store vesting contract data for token unlocks?
The primary table is `erc20_ethereum.evt_Transfer`. For tokens in Spellbook, use specific tables like `arbitrum.ARB_evt_Transfer`. Custom vesting contracts may emit events captured in `call_evt` tables.
Can I get real-time unlock alerts from Dune dashboards?
Yes, by using Dune's API (premium) or by embedding your dashboard in a tool like Zapier. You can also manually monitor via the dashboard's scheduled refresh.
How do I distinguish between cliff and linear unlocks in my Dune query?
Examine the pattern of daily transfer amounts: one large outlier indicates a cliff; consistent small amounts indicate linear. You can also filter by specific contract addresses known for one type.
Is it possible to track unlocks for any ERC-20 token on Dune?
Yes, as long as the token's transfers are available in Dune's indexed data (most popular ones are). You'll need the vesting contract address and proper decimal handling.
Related reading
Track the entities behind the concepts
DeFi Intel maps 11,000+ protocols, tokens and companies to a typed knowledge graph — with live data, incidents and regulation.