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

QDMY

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

Lifecycle

  1. first pin received 2026-09-06 13:59:23 UTC · 20 h ago #9320 via layerzero
  2. token discovered 2026-09-05 12:33:06 UTC · 2 d ago 2 contracts today
  3. first liquid pending not yet
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

ethereum canonical via layerzero
9
0x5f195d1b998d2964928c422f93130e762cb1c666 open
illiquidpools hold $0, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"QDMY","source_tx":null,"message_id":"1397114819504504895","message_ts":"2025-07-22T07:15:30","source_url":"https://layerzeroscan.com/address/0xFF1d88E33770D7D649D11e57931B70De88773425","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1397114819504504895","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0x1a7b1b76a80cbe54cddfb7b5da6150ac75844f7f96b9c1d7cd63a520ef63c1fe","from":"bridge_pin"}
registry+5{"via":"OFTAdapter.token","adapter":"layerzero","oftAdapter":"0xff1d88e33770d7d649d11e57931b70de88773425"}
polygon canonical via layerzero
6
0x4e839ac433f01ca868a0cd1122989412e7f8b186 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":"QDMY","source_tx":null,"message_id":"1397114819504504895","message_ts":"2025-07-22T07:15:30","source_url":"https://layerzeroscan.com/address/0xFF1d88E33770D7D649D11e57931B70De88773425","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1397114819504504895","source_kind":"oft_address","curator_liquidity":false}
peer_map+5{"via":{"address":"0xff1d88e33770d7d649d11e57931b70de88773425","chainSlug":"ethereum"},"adapter":"layerzero","oftAdapter":"0x0c071cdf40be7fd754363eec3c8595679ac51fe7","unwrappedTo":"0x4e839ac433f01ca868a0cd1122989412e7f8b186"}

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 ethereum 1 of 1 reachable
polygon layerzero 0x1a7b1b76… 20 h ago
from polygon 0 of 1 reachable

No transfer has been seen leaving polygon.

show 1 unreachable hide unreachable
ethereum no transfer seen

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9320 20 h ago layerzeroethereum → polygon 0x1a7b1b76…63c1fe DISCOVERED 10 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.