tracced
Update 0.7.10 is outRead what's new

Limits

tracced is early, so the caps are small while the load is watched. They will grow.

Free for everyone

The demo token, every finished result, every page, and the chart of any token. Opening a finished analysis costs nothing and needs no account β€” that is what makes a shared link work. A finished analysis stays as it was run, whoever ran it: its range does not move, and a different range is a new row beside it.

Needs a wallet

Running a new analysis. The wallet signs a message: no transaction, no fee. You are asked at the moment you press Get wallets, not before, and the range you marked survives the sign-in.

The daily count of new analyses is per person, not per wallet: connecting another wallet in the same browser adds nothing. To know the browser again, the first analysis leaves a cookie holding a random number and nothing else; it is not used for analytics. One network has its own, higher count, because an office or a phone carrier puts many people behind one address. Every count resets at midnight UTC, and the page shows how many are left. A run that fails early, or is cut short by a server restart, gives its analysis back; one that fails once it has done real work counts toward the day.

Connect your wallet: 10 analyses a day for active wallets. A wallet with no trading history may get fewer. To set the count, we read the wallet's public on-chain history when it presses Get wallets, and use it for nothing else.

Need more than the day gives? The window that says the count is used up has a Write to us button: tell us how you use tracced, and we raise the limit.

Beta testers the owner invites have no daily count. The limits on a single run apply to them as to everyone.

Loading what a result does not hold yet in a wallet card: the wallet's last 30 days on every token, and its age and first funder when the analysis has not checked them. What someone has already loaded is free for everyone: the 30 days are kept for a day, and the age and funder stay in the result.

To count a sale at its real cost, a card also reads the wallet's earlier trades of the tokens it sold in those days but bought before them: up to 25 tokens a card, from the site's day rather than yours.

Limit Value
New analyses a day, per person: wallet and browser count together 10
New analyses a day from one network 20
New analyses a day on the whole site, while the month's requests last 100
Ranges per token 5
Longest range 6 hours
Wallets that get exact exits 2,000
Smallest position in the table $20 bought inside the range
Wallets whose age is checked with the analysis, first by PnL 200
Other wallets checked from their cards, per person a day, and per network 50
Changes to your watchlist, tags and notes, and exports, per wallet a day 500
Questions to the AI agent, per person a day 10
Results the agent writes its cards for, per person a day (cards someone already opened are free) 20

πŸ“ These numbers are the live settings

The table is rendered from the same configuration the site runs on, so it cannot drift from what actually happens.

Why they exist

Reading a new token's history costs real money. The first analysis of a busy token is the expensive one. Every further range on the same token is nearly free, because its trades are already stored.

Near the end of a heavy month new analyses may wait; the demo, every finished result and every chart stay open.

Which wallets get exact exits

The largest buyers of the range. The rest keep their entry; their Sold and PnL show β€”, because we did not read their sells.

On some tokens everyone gets exact exits and this cap does not apply at all. The line above the table always says which happened.

Live on Solana DemoDocsHow it worksThe projectWhat's newContact v0.7 XTelegramGitHub