Home / Tokens / Avalanche C-Chain / JOE

Token coverage · Avalanche C-Chain

JOE (JoeToken) on Avalanche C-Chain

Data as of 01 Nov 2026, 21:49 UTC · refreshed every 12 h · source: public catalog

JOE: 2,080 verified swaps across 4 pools on Avalanche C-Chain since 29 Oct 2026, covered until 01 Nov 2026, 16:00 UTC. 3 anomaly findings, each with an Evidence Card.

Facts

Token

JOE (JoeToken)

Network

Avalanche C-Chain (EVM, chain id 43114)

Contract address

0x6e84a6216ea6dacc71ee8e6b0a5b7322eebc0fdd

Status

Available at least 72 hours of verified history

Coverage window

29 Oct 2026, 00:00 UTC → 01 Nov 2026, 16:00 UTC

Hours of history

88

Verified swaps

2,080

Pools measured

4

Anomaly findings

3

Latest finding

volume decline (01 Nov 2026)

Verified swaps are swaps decoded directly from the chain in pools that passed verification; findings describe the verified pools that were measured, never a token's whole market, and none is an accusation.

What an Evidence Card for JOE contains

Every anomaly finding comes with an Evidence Card that answers five questions, built only from stored data. A value that cannot be determined is shown as unknown, with the reason.

1. What was observed? The metric and its unit, the observed value against the expected baseline, and the window in UTC.
2. Where is the evidence? Network, chain id and the token's contract; the block range; each measured pool with its protocol and decoder family; the swap count and the five largest transactions; the RPC providers and ingestion runs covering the window.
3. How was it computed? The method and its version, the baseline window and value (frozen when the anomaly starts), the parameters and the detector's facts.
4. How much can we trust it? Hours expected against hours fully covered, every gap, the checks that passed, and the caveats and alternative explanations.
5. How can it be checked independently? The detection SQL with its SHA-256, and a recipe for any public JSON-RPC node that needs no access to our database.

Check it on a public node

The reproduction recipe re-reads the same swap logs from any public JSON-RPC endpoint:

// eth_getLogs over the measured pools, one Swap topic per decoder family
{"method": "eth_getLogs", "params": [{
  "address":   ["<measured pools>"],
  "topics":    ["<Swap event topic>"],
  "fromBlock": "<first block, hex>",
  "toBlock":   "<last block, hex>"
}]}

The pool list, the exact block range and the expected swap count for each finding are in the Evidence Snapshot and in the application.

Get the evidence

Prices and plans: pricing. USD values are not part of the evidence.