Token Dashboard
tokens
2813
contracts
8317
confirmed
5695 of 8317
chains seen
14
unmeasured
189
queued
0

HUNT

HuntToken
status
fully reported2/2 checked · 2 liquid · 2 reported · hot
first bridged
2 d ago
arrived via
base_bridge
contracts
3 on 2 chains
confirmed by a transfer
3 of 3
liquidity
2 of 2 chains checked · 2 liquid
checking
hot
already alerted on
base, ethereum
pins
4

Lifecycle

  1. first pin received 2026-09-02 23:49:29 UTC · 2 d ago #3839 via base_bridge
  2. token discovered 2026-09-03 04:38:04 UTC · 2 d ago 3 contracts today
  3. first liquid 2026-09-04 05:37:25 UTC · 21 h ago a chain quoted liquid
  4. first alert 2026-09-04 05:37:25 UTC · 21 h ago multi_chain_liquid, sent 21 h ago
  5. reported chains base, ethereum — 2 of 2

Where this token lives

More than one contract on base (2). That is allowed — a bridge wrapper and the canonical token are separate contracts and trade in separate pools (§3) — but it is also what a clone reusing the ticker looks like. Compare the evidence below: a contract confirmed by the bridge itself outranks one matched only by symbol.

base mint burn via base_bridge 8
0x37f0c2915cecc7e977183b8543fc0864d03e064c open
liquidlast verified 21 h ago

2 of 2 sources are protocol-attested — a contract confirmed this link.

registry+3{"tx":"0x44500f04f4db2bb28f292b61bf07ca698475d719931089d02bd76493d1f8ae36","from":"bridge_pin"}
derivation+5{"via":"remoteToken","adapter":"base_bridge"}
ethereum canonical via base_bridge 5
0x9aab071b4129b083b01cb5a0cb513ce7eca26fa5 open
liquidlast verified 21 h ago

1 of 1 sources are protocol-attested — a contract confirmed this link.

derivation+5{"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0x37f0c2915cecc7e977183b8543fc0864d03e064c"}
base mint burn via base_bridge shadowed · not checked 5
0x102a7fe099ca1d917562080a9bfd6a0dfd711b78 open
liquidlast verified 22 h ago

Every source here is an inference. A contract on this chain has not confirmed the link itself.

bridge_transfer+5{"tx":"0x6e440d07dc815f7ebd15ccb970b2aeb2e82e3d4fc3158157fe44814cb2a5e6b7","adapter":"base_bridge"}

How it moves between chains

Each chain lists the directions a transfer has actually been seen taking. Directions with no transfer behind them are folded away per card and counted in its header. Derived routes are not shown at all.

from base 1 of 1 reachable
ethereum base_bridge 0x44500f04… 2 d ago
from ethereum 1 of 1 reachable
base base_bridge 0x80accdb7… 2 d ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#6790 2 d ago base_bridgeethereum → base 0xe41a5d5c…2f9638 SKIPPED_DUPLICATE 2 h 56 min
#6474 2 d ago base_bridgebase → ethereum 0x046f8fc7…4fe24f SKIPPED_DUPLICATE 2 h 2 min
#5837 2 d ago base_bridgebase → ethereum 0x85790b83…a95811 SKIPPED_DUPLICATE 1 h 39 min
#3839 2 d ago base_bridgebase → ethereum 0x44500f04…f8ae36 DISCOVERED 4 h 49 min

Alerts

KindCreatedStateSentTelegram id
multi_chain_liquid21 h ago SENT 21 h ago435

Exclude this token if it is junk or not worth watching. Liquidity stops being checked and nothing more is searched for it; its contracts, evidence, routes and history stay, its pins are still recorded, and it can be tracked again from the Excluded page.

Every address above came from an on-chain read. The evidence trail shows which read produced it.