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

CRCLon

Circle Internet Group (Ondo Tokenized)
status
unmeasured3/3 checked · 0 liquid · warm
first bridged
2 d ago
arrived via
layerzero
contracts
5 on 3 chains
confirmed by a transfer
5 of 5
liquidity
3 of 3 chains checked · 0 liquid · 2 unmeasured
checking
warm
already alerted on
nothing yet
pins
3

Lifecycle

  1. first pin received 2026-09-03 06:06:42 UTC · 2 d ago #7727 via layerzero
  2. token discovered 2026-09-02 21:38:30 UTC · 2 d ago 5 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 ethereum (2), 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 mint burn via layerzero 5
0xf8589b526fdd65f7f301c605a6e04f0f1b4b3620 open
unknownBALANCE_READ_FAILED — not a negative result

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

bridge_transfer+5{"tx":"0xea47585ad88f6225a0583f40f22755a175bbfac0b591104f49d243fa244563a4","adapter":"layerzero"}
hyperevm mint burn via layerzero 5
0x13a81c5e8b4ab05fc721dff7ba95e250b29458f8 open
illiquidpools hold $0, under the floor

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

bridge_transfer+5{"tx":"0x30f7c0f4af91dae880c7ea10dbc21890625ded4ca7590b7647c86caa6063ca8a","adapter":"layerzero"}
binance mint burn via layerzero shadowed · not checked 5
0x992879cd8ce0c312d98648875b5a8d6d042cbf34 open
unknownBALANCE_READ_FAILED — not a negative result

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

bridge_transfer+5{"tx":"0x09d330ffc4ed374164b7bf2cf5624df2676064da5d88bb3f3992c216b48dc348","adapter":"layerzero"}
ethereum canonical via layerzero 3
0xf042cfa86cf1d598a75bdb55c3507a1f39f9493b open
illiquidpools hold $0, under the floor

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

registry+3{"tx":"0xea47585ad88f6225a0583f40f22755a175bbfac0b591104f49d243fa244563a4","from":"bridge_pin"}
ethereum canonical via layerzero shadowed · not checked 3
0x3632dea96a953c11dac2f00b4a05a32cd1063fae open
unknownBALANCE_READ_FAILED — not a negative result

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

registry+3{"tx":"0x09d330ffc4ed374164b7bf2cf5624df2676064da5d88bb3f3992c216b48dc348","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 binance 2 of 2 reachable
ethereum layerzero 0x9c528b11… 2 d ago
hyperevm layerzero 0x202851ef… 30 h ago
from ethereum 2 of 2 reachable
binance layerzero 0x09d330ff… 2 d ago
hyperevm layerzero 0x30f7c0f4… 2 d ago
from hyperevm 2 of 2 reachable
binance layerzero 0x38381ff4… 2 d ago
ethereum layerzero 0x348dd8de… 2 d ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8532 2 d ago layerzerohyperevm → binance 0x1fd2ab9e…1bb876 SKIPPED_DUPLICATE 14 h
#8050 2 d ago layerzerobinance → hyperevm 0x87adf98c…caa757 SKIPPED_DUPLICATE 11 h
#7727 2 d ago layerzerobinance → ethereum 0x75c6be3a…0eb06e SKIPPED_DUPLICATE 10 h

Merge history

WhenWinnerLoserContracts movedEvidenceState
2 d ago #384 #81 3 {"tx":"0x30f7c0f4af91dae880c7ea10dbc21890625ded4ca7590b7647c86caa6063ca8a","bridge":"layerzero","reason":"a delivered transfer connected contracts held by two assets","endpoint":"hyperevm:0x13a81c5e8b active

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.