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

TSLA

Tesla - Wagyu.xyz
status
liquid2/2 checked · 1 liquid · warm
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
warm
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-03 06:07:34 UTC · 2 d ago #8490 via ccip
  2. token discovered 2026-09-02 21:39:52 UTC · 2 d ago 3 contracts today
  3. first liquid 2026-09-04 22:57:58 UTC · 3 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 hyperevm (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.

hyperevm mint burn via layerzero decimals differ from source 5
0x18bce0f2ac30b4749d2e8c43468e9da88e229afd 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":"5zvHG9pif2RfTD7y2xDJCmneWa5yEbQpDmXJm44nS1CAxwXwUaTog9RxmDFkphgqr4hZTPQJfUV6vZJaaGupZr31","adapter":"layerzero"}
hyperevm canonical via layerzero shadowed · not checked 3
0x3727c797073840936e3c18b4088f3574cd1a72a3 open
illiquidpools hold $0, under the floor

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

registry+3{"tx":"0x67503d0fcdd777532d37a109a7f7655da51b5811a29a28d2f2b25e12ce1ad6c6","from":"bridge_pin"}
solana canonical via ccip 13
XsDoVfqeBukxuZHWhdvWHBhgEHjGNst4MLodqsJHzoB open
liquid3 bps · 0.03% via jupiter

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

peer_map+5{"via":{"address":"0x3727c797073840936e3c18b4088f3574cd1a72a3","chainSlug":"hyperevm"},"adapter":"layerzero","oftStore":"DKrEzUwkUSmNQDrp6fzmJDZTCbG8BazqD2SgmnpRPiAx","resolvedMint":"XsDoVfqeBukxuZHWhdvWHBhgEHjGNst4MLodqsJHzoB"}
registry+5{"tx":"eD2Fhex5cLsyqsknkzaxUSSmRqgVM7p5kTp3hsJC2QweQdP9mSff6aZ7vUZW8NxiubfuhNVChq5dWn1HMywx8Eh","via":"solana_tx_parse"}
registry+3{"tx":"eD2Fhex5cLsyqsknkzaxUSSmRqgVM7p5kTp3hsJC2QweQdP9mSff6aZ7vUZW8NxiubfuhNVChq5dWn1HMywx8Eh","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 hyperevm 1 of 1 reachable
solana layerzero 0x3a894a89… 2 d ago
from solana 1 of 1 reachable
hyperevm layerzero 5zvHG9pif2… 2 d ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8490 2 d ago ccipsolana → ethereum eD2Fhex5cL…ywx8Eh DISCOVERED 14 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.