Token Dashboard
tokens
1957
contracts
6128
confirmed
5678 of 6128
chains seen
14
unmeasured
174
queued
0

FET

Fetch
status
liquid3/3 checked · 1 liquid · hot
first bridged
18 h ago
arrived via
portal_bridge
contracts
4 on 3 chains
confirmed by a transfer
3 of 4
liquidity
3 of 3 chains checked · 1 liquid
checking
hot
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-03 06:18:21 UTC · 34 h ago #9059 via portal_bridge
  2. token discovered 2026-09-03 22:21:34 UTC · 18 h ago 4 contracts today
  3. first liquid 2026-09-04 16:11:34 UTC · 1 min ago a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

More than one contract on ethereum (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.

binance canonical via portal_bridge 8
0x031b41e504677879370e9dbcf937283a8691fa7fsame open
liquid78 bps · 0.78% via kyberswap

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

registry+3{"tx":"0x4997cd635ec9c88839349df7ea7a1eb2569c9004c5b66e10974be6c46f31fdd9","from":"bridge_pin"}
derivation+5{"via":"origin_from_index","adapter":"portal_bridge","originChainId":4}
ethereum lock mint wrapper via portal_bridge 5
0xdef43530f2b4d347c91942162fb1205dbc2d8543 open
illiquidpools hold $0, under the floor

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

derivation+5{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0x3ee18b2214aff97000d974cf647e7c347e8fa585","originChainId":4}
polygon lock mint wrapper via portal_bridge 5
0x205b328e408246c77d39bca9f23560847e54de3d open
illiquidpools hold $0, under the floor

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

derivation+5{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0x5a58505a96d1dbf8df91cb21b54419fc36e93fde","originChainId":4}
ethereum mint burn shadowed · not checked potential · no transfer seen 3
0x031b41e504677879370e9dbcf937283a8691fa7fsame open
illiquidpools hold $0, under the floor

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

same_address+3{"chain":"ethereum"}

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 binance 2 of 2 reachable
ethereum portal_bridge 0x4997cd63… 18 h ago
polygon portal_bridge 0x11416cd1… 18 h ago
from ethereum 1 of 2 reachable
binance portal_bridge 0x1c68237c… 18 h ago
show 1 unreachable hide unreachable
polygon no transfer seen
from polygon 1 of 2 reachable
binance portal_bridge 0x0a882bf8… 18 h ago
show 1 unreachable hide unreachable
ethereum no transfer seen

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9059 34 h ago portal_bridgebinance → ethereum 0x4997cd63…31fdd9 DISCOVERED 16 h

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.