Token Dashboard
tokens
1960
contracts
6137
confirmed
5685 of 6137
chains seen
14
unmeasured
175
queued
0

WQIE

WQIE
status
illiquid2/2 checked · 0 liquid · warm
first bridged
24 h ago
arrived via
debridge
contracts
3 on 2 chains
confirmed by a transfer
2 of 3
liquidity
2 of 2 chains checked · 0 liquid
checking
warm
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-03 06:07:54 UTC · 2 d ago #8732 via debridge
  2. token discovered 2026-09-03 21:08:34 UTC · 24 h ago 3 contracts today
  3. first liquid pending not yet
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

More than one contract on binance (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 lock mint wrapper via debridge 10
0xedf16c976fab230354ffe88a32d850a9c808516d open
illiquidpools hold $0, under the floor

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

registry+5{"via":"submission_claim","adapter":"debridge","claimTx":"0xdd351d813a0aade07c33bf3def33bebf69cf6195365fde5b8328831b1a014376"}
derivation+5{"via":"Gate.getDebridge","gate":"0x43de2d77bf8027e25dbd179b491e8d64f38398aa","adapter":"debridge","debridgeId":"0x8c1c4dcceed205098e6332e2c997516a0ca6da35e6e2549de61ad8c23f20d47c"}
ethereum canonical via debridge 3
0x775acf0fae2b97789ea58e775789925ade06b867same open
illiquidpools hold $0, under the floor

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

registry+3{"tx":"0xb2f628b25ee11d8c60dd3e551035fc377c1f6ef083715cca0442186cb47c72ba","from":"bridge_pin"}
binance mint burn shadowed · not checked potential · no transfer seen 3
0x775acf0fae2b97789ea58e775789925ade06b867same 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":"binance"}

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 0 of 1 reachable

No transfer has been seen leaving binance.

show 1 unreachable hide unreachable
ethereum no transfer seen
from ethereum 1 of 1 reachable
binance debridge 0xb2f628b2… 24 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8732 2 d ago debridgeethereum → binance 0xb2f628b2…7c72ba DISCOVERED 15 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.