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

TRX

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

Lifecycle

  1. first pin received 2026-09-06 13:59:53 UTC · 20 h ago #9351 via layerzero
  2. token discovered 2026-09-05 12:33:06 UTC · 2 d ago 3 contracts today
  3. first liquid 2026-09-07 10:21:47 UTC · 2 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 avalanche (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.

ethereum canonical via layerzero decimals differ from source
6
0x50327c6c5a14dcade707abad2e27eb517df87ab5 open
liquid52 bps · 0.52% via kyberswap

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

discord+1{"notes":[],"proven":false,"ticker":"TRX","source_tx":null,"message_id":"1413164623967817940","message_ts":"2025-09-04T14:11:41","source_url":"https://layerzeroscan.com/address/0x54eb5a7Ec2FB2212E089ed794a6999D281345F5c","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1413164623967817940","source_kind":"oft_address","curator_liquidity":true}
peer_map+5{"via":{"address":"0xc5718c4c91e9d051b082e02b1138ab5b6a01dcd1","chainSlug":"avalanche"},"adapter":"layerzero","oftAdapter":"0x54eb5a7ec2fb2212e089ed794a6999d281345f5c","unwrappedTo":"0x50327c6c5a14dcade707abad2e27eb517df87ab5"}
avalanche mint burn via layerzero
5
0x24de8dcc7c0621a57e58ce8388cdeae42217ba3a 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":"0x1cec74900d6ba39d2f867bbff50973b584ede15667226e438caab24e66756197","adapter":"layerzero"}
avalanche canonical via layerzero
4
0xc5718c4c91e9d051b082e02b1138ab5b6a01dcd1 open
illiquidpools hold $28, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"TRX","source_tx":null,"message_id":"1413164623967817940","message_ts":"2025-09-04T14:11:41","source_url":"https://layerzeroscan.com/address/0x54eb5a7Ec2FB2212E089ed794a6999D281345F5c","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1413164623967817940","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0x5f6501025dbf1384dd0b96e27a5f9fea94d61542b522bbcc72190334dd88a8b6","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 avalanche 1 of 1 reachable
ethereum layerzero 0x5f650102… 20 h ago
from ethereum 1 of 1 reachable
avalanche layerzero 0x1cec7490… 20 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9351 20 h ago layerzeroavalanche → ethereum 0x5f650102…88a8b6 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.