Token Dashboard
tokens
2811
contracts
8313
confirmed
5691 of 8313
chains seen
14
unmeasured
186
queued
0

SUPER

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

Lifecycle

  1. first pin received 2026-09-03 06:06:13 UTC · 2 d ago #6308 via layerzero
  2. token discovered 2026-09-02 04:45:17 UTC · 3 d ago 5 contracts today
  3. first liquid 2026-09-04 05:18:25 UTC · 20 h ago a chain quoted liquid
  4. first alert 2026-09-04 05:18:25 UTC · 20 h ago multi_chain_liquid, sent 20 h ago
  5. reported chains avalanche, base, ethereum, polygon — 4 of 4

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.

ethereum canonical via layerzero 21
0xe53ec727dbdeb9e2d5456c3be40cff031ab40a55 open
liquidlast verified 20 h ago

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

registry+3{"tx":"0x26003b7afce00e512424a9933f2a864585b0dec7871725f2585faba7d63b5031","from":"bridge_pin"}
derivation+5{"via":"pin_source","adapter":"base_bridge"}
registry+3{"tx":"0xb60ff98b8e856da7bff1337d8e3297a3cc28f71284b2a47c609f3c0f4e9ebfbd","from":"bridge_pin"}
derivation+5{"via":"pin_source","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}
peer_map+5{"via":{"address":"0x09fa58228bb791ea355c90da1e4783452b9bd8c3","chainSlug":"avalanche"},"adapter":"layerzero","oftAdapter":"0x7217711a84b12d95c5bab6ab981d266456fbef56","unwrappedTo":"0xe53ec727dbdeb9e2d5456c3be40cff031ab40a55"}
base mint burn via base_bridge 5
0x391359ab0ccef572dcac78f74e47d7c06db0b982 open
liquidlast verified 20 h ago

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

derivation+5{"via":"delivery_tx","adapter":"base_bridge","deliveryTx":"0xabb0b9a4cff5a15ede265fd7d172f7ac9fe78b896b488b878fdbe5f07e3e545f","confirmedBy":"remoteToken"}
base mint burn via base_bridge shadowed · not checked 5
0x576b74d41c47e96673954d8cdba0bd1cf1677b15 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":"0x5bc2b96d873d64adafdbd8e406fcfe0bb1e48dedd7bb451c3c5cebc20dc68030","adapter":"base_bridge"}
polygon mint burn via polygon_bridge 5
0xa1428174f516f527fafdd146b883bb4428682737 open
liquidlast verified 20 h ago

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

derivation+5{"via":"rootToChildToken","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}
avalanche canonical via layerzero 3
0x09fa58228bb791ea355c90da1e4783452b9bd8c3 open
liquidlast verified 20 h ago

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

registry+3{"tx":"0x1339aa9338cd252631f751b5f66bdaff613b93fdebfee4ee3c14948872f19a83","from":"bridge_pin"}

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 avalanche 1 of 3 reachable
ethereum layerzero 0x1339aa93… 2 d ago
show 2 unreachable hide unreachable
base no transfer seen
polygon no transfer seen
from base 1 of 3 reachable
ethereum base_bridge 0x2578fbdc… 2 d ago
show 2 unreachable hide unreachable
avalanche no transfer seen
polygon no transfer seen
from ethereum 3 of 3 reachable
avalanche layerzero 0x463a77e6… 32 h ago
base base_bridge 0x26003b7a… 3 d ago
polygon polygon_bridge 0xb60ff98b… 2 d ago
from polygon 0 of 3 reachable

No transfer has been seen leaving polygon.

show 3 unreachable hide unreachable
avalanche no transfer seen
base no transfer seen
ethereum no transfer seen

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#7986 2 d ago layerzeroethereum → avalanche 0xb0ce2711…be6cf9 SKIPPED_DUPLICATE 11 h
#6308 2 d ago layerzeroavalanche → ethereum 0x1339aa93…f19a83 DISCOVERED 46 min

Alerts

KindCreatedStateSentTelegram id
multi_chain_liquid20 h ago SENT 20 h ago358

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.