Token Dashboard
tokens
2788
contracts
8845
confirmed
7202 of 8845
chains seen
14
unmeasured
92
queued
0

UB

name unknown
status
illiquid3/3 checked · 0 liquid · warm
first bridged
2 d ago
arrived via
layerzero
contracts
4 on 3 chains
confirmed by a transfer
4 of 4
liquidity
3 of 3 chains checked · 0 liquid
checking
warm
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-06 13:59:55 UTC · 20 h ago #9353 via layerzero
  2. token discovered 2026-09-05 12:33:06 UTC · 2 d ago 4 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 canonical via layerzero
1
0x1b3dc4daa470fa33f3c2367efc6f1d3287acac51 open
illiquidpools hold $0, under the floor

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

discord+1{"notes":["#3"],"proven":false,"ticker":"UB","source_tx":null,"message_id":"1415452473623183471","message_ts":"2025-09-10T21:42:47","source_url":"https://layerzeroscan.com/address/0x88B77551320EC0BfE701EDA719186Fe53BACdD2b","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1415452473623183471","source_kind":"oft_address","curator_liquidity":false}
ethereum canonical via layerzero
1
0x229e0bb68c3d34a5160da79c0748f3e21efcd558 open
illiquidpools hold $0, under the floor

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

discord+1{"notes":["#3"],"proven":false,"ticker":"UB","source_tx":null,"message_id":"1415452473623183471","message_ts":"2025-09-10T21:42:47","source_url":"https://layerzeroscan.com/address/0x88B77551320EC0BfE701EDA719186Fe53BACdD2b","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1415452473623183471","source_kind":"oft_address","curator_liquidity":false}
binance canonical via layerzero
6
0x1b600603bc1629cc14963a764382bb5ebbde5c02 open
illiquidpools hold $0, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"UB","source_tx":null,"message_id":"1415283920806871111","message_ts":"2025-09-10T10:33:01","source_url":"https://layerzeroscan.com/address/0x9C172C5c23f23aF104a62DaB3FE164f96d3dd5Cc","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1415283920806871111","source_kind":"oft_address","curator_liquidity":false}
peer_map+5{"via":{"address":"0x88b77551320ec0bfe701eda719186fe53bacdd2b","chainSlug":"base"},"adapter":"layerzero","oftAdapter":"0x9c172c5c23f23af104a62dab3fe164f96d3dd5cc","unwrappedTo":"0x1b600603bc1629cc14963a764382bb5ebbde5c02"}
base canonical via layerzero
5
0x88b77551320ec0bfe701eda719186fe53bacdd2b open
illiquidpools hold $0, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"UB","source_tx":null,"message_id":"1415283920806871111","message_ts":"2025-09-10T10:33:01","source_url":"https://layerzeroscan.com/address/0x9C172C5c23f23aF104a62DaB3FE164f96d3dd5Cc","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1415283920806871111","source_kind":"oft_address","curator_liquidity":false}
discord+1{"notes":["#3"],"proven":false,"ticker":"UB","source_tx":null,"message_id":"1415452473623183471","message_ts":"2025-09-10T21:42:47","source_url":"https://layerzeroscan.com/address/0x88B77551320EC0BfE701EDA719186Fe53BACdD2b","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1415452473623183471","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0x2205c276f7fe5fbb050f578b684d92234f77e80f406286c98814351b4797ab5d","from":"bridge_pin"}

How it moves between chains

Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.

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 2 reachable
binance layerzero 0x2205c276… 20 h ago
show 1 unreachable hide unreachable
ethereum no transfer seen
from binance 1 of 2 reachable
base layerzero 0xecae0834… 20 h ago
show 1 unreachable hide unreachable
ethereum no transfer seen
from ethereum 1 of 2 reachable
binance layerzero 0xa0f5f804… 20 h ago
show 1 unreachable hide unreachable
base no transfer seen

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9353 20 h ago layerzerobase → binance 0x2205c276…97ab5d DISCOVERED 13 min

Verdict. Add it if this is the token you want to watch; reject it if any contract is a twin, a clone or junk — a rejected token stays checked but is not alerted on again.

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.