Token - Wallet Tags Tracker Details

Drill into the Wallet Tags Tracker: for each time bucket, list the individual tagged wallets that traded, with their per-wallet buy/sell volume and transaction counts. Use it to see exactly which developers, snipers, or smart-money wallets were active in a given candle.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

One row per wallet, per bucket. The response is a list of time buckets (items); each bucket has a unix_time (bucket open time) and a wallets array of the tagged wallets that traded in it.

  • Each wallet row carries its own volume_buy / volume_sell (token amounts) and volume_buy_usd / volume_sell_usd, plus tx_buy_count / tx_sell_count.
  • tags lists the wallet's tags for this token (dev, sniper, smart_trader). A wallet can carry several.
  • is_top_10_holder appears only when top_10_holder=true, flagging wallets that are among the token's top 10 holders.

Reading the numbers. Volumes are gross and leg-based — a transaction that both buys and sells counts on both sides, with no netting. tx_buy_count / tx_sell_count count that wallet's buy/sell transactions in the bucket. Wallets are ordered by USD volume descending and capped per bucket by limit_wallet; buckets with no activity are omitted. At most limit_bucket buckets are returned — while has_more is true, pass next_time_from back as time_from to page forward.

Use Cases 💡
  • Drill into a single candle to see exactly which developers, snipers, and smart-money wallets bought or sold.
    • Turn a volume spike from the summary endpoint into the actual wallet addresses behind it — ready to label, follow, or alert on.
    • Track a known set of wallets over time by passing wallets=, watching how specific actors accumulate or exit bucket by bucket.
    • Build wallet-level launch forensics and post-mortems that name who drove each phase, not just how much volume moved.
How to Use 🛠️
  • Provide a token_address, a required time_from unix timestamp in seconds, and a required time_frame. Omit time_to to read activity up to now.
    • Pick time_frame by the question you're asking: 1s30s for launch forensics, 1m30m for intraday rotation, 1h1M for trend.
    • Use tags=dev,sniper,smart_trader to narrow the cohorts, or wallets=addr1,addr2 (up to 50) to restrict to specific addresses.
    • Set min_volume_usd to drop dust wallets, and top_10_holder=true to flag top holders via is_top_10_holder.
    • Tune limit_wallet (wallets per bucket, up to 50) and limit_bucket (buckets returned, up to 300). While has_more is true, pass next_time_from back as time_from to page forward.
Best Practices ✅
  • Use the Wallet Tags Tracker (summary) to spot the interesting buckets first, then drill into those windows here for the wallet-level detail.
    • Raise min_volume_usd to focus on wallets that actually moved the market and keep noise out of dashboards.
    • Pass wallets= to follow a known cohort — insiders, a dev's set, or flagged smart money — across every bucket in the range.
    • Keep limit_wallet tight for UI tables and page buckets with next_time_from rather than requesting an oversized range at once.
Limitations ⚠️
  • Solana only.
    • Supported tags are dev, sniper, and smart_trader.
    • Maximum range per time_frame — seconds: 30 days, minutes: 60 days, hours: 90 days, 1D/1W/1M: 365 days. Exceeding it returns 400.
    • Some highly held or high-cost tokens (wSOL, USDC, USDT, BONK) are not supported for this endpoint.

Query Params
string
required

Token mint address

integer
required

Start of the range, as a unix timestamp in seconds.

integer

End of the range, as a unix timestamp in seconds. Defaults to now. Must be greater than time_from, and within the time_frame's maximum range.

string
enum
required

Size of each time bucket. Must match the bucket the drilldown is read against.

tags
array of strings

Comma-separated wallet tags to restrict the response to. Defaults to all supported tags.

tags
Allowed:
wallets
array of strings

Comma-separated wallet addresses to restrict the response to. Up to 50 addresses.

wallets
number
≥ 0
Defaults to 0

Only include wallets whose USD volume in a bucket is at least this value.

boolean
Defaults to false

Set to true to flag wallets that are among the token's top 10 holders (is_top_10_holder).

integer
1 to 50
Defaults to 10

Max wallets returned per bucket, ordered by USD volume descending. 1-50.

integer
1 to 300
Defaults to 300

Max time buckets returned. 1-300. Use next_time_from to page beyond this.

Headers
string
enum
Defaults to solana

Solana network only.

Allowed:
Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json