tokenWalletStats

​

Example

{
  tokenWalletStats(
    input: {
      tokenAddress: "FvMLDEUDKUr9C34e8Nynz5Aqfdk34a2RBKQxygLpfomo"
      networkId: 1399811149
    }
  ) {
    tokenId
    tokenTotalSupply
    sniperCount
    sniperHeldPercentage
    sniperAddresses
    bundlerCount
    bundlerHeldPercentage
    bundlerAddresses
    insiderCount
    insiderHeldPercentage
    insiderAddresses
    suspiciousCount
    suspiciousHeldPercentage
    suspiciousAddresses
    devAddress
    devHeldPercentage
    devHeldAmount
  }
}

​

Usage Guidelines

• Pass the token’s contract address and networkId. The response is per token: a wallet’s label here says nothing about its behavior on other tokens
• Every count, percentage, amount, and address list covers wallets that still hold the token. A labelled wallet that sold its whole balance drops out, so the numbers fall over time as those wallets sell
• Held percentages are measured against tokenTotalSupply. Amounts are unshifted raw units
• suspicious* is the deduplicated union of the sniper, bundler, and insider cohorts, not the sum of the three
• Address lists are capped at 200 per cohort. The counts and percentages still cover every labelled holder
• devAddress is empty when the creator is unknown. The creator’s wallet can also appear in sniperAddresses if it bought within the sniper window
• For the same counts and percentages without addresses, use the matching fields on filterTokens (launchpad tokens only), pairMetadata (walletActivity), or the launchpad subscriptions
• How each label is defined is explained in Snipers, bundlers, and insiders

​

Troubleshooting Tips

​

Related Recipes

• Discover tokens: How snipers, bundlers, insiders, and the suspicious roll-up are defined
• Launchpad lifecycle: Track tokens from creation through graduation