Token Dashboard
tokens
2788
contracts
8846
confirmed
7203 of 8846
chains seen
14
unmeasured
94
queued
0

NTT

name unknown
status
illiquid2/2 checked · 0 liquid · warm
first bridged
2 d ago
arrived via
portal_bridge
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:18 UTC · 21 h ago #9310 via portal_bridge
  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

arbitrum canonical via portal_bridge
10
0x9af6c42076cf1c54752cb628d6ce235e2d71814dsame open
illiquidpools hold $0, under the floor

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

discord+2{"notes":["**Wormhole NTT**"],"proven":true,"ticker":"NTT","source_tx":"0x55d0bd6b2d068dfd4e89336b11e59f315f6d25906be9db4101bf399366b3b528","message_id":"1393550412069736511","message_ts":"2025-07-12T11:11:49","source_url":"https://wormholescan.io/#/tx/0x55d0bd6b2d068dfd4e89336b11e59f315f6d25906be9db4101bf399366b3b528?network=Mainnet","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1393550412069736511","source_kind":"wormhole_tx","curator_liquidity":false}
registry+3{"tx":"0x55d0bd6b2d068dfd4e89336b11e59f315f6d25906be9db4101bf399366b3b528","from":"bridge_pin"}
derivation+5{"via":"origin_from_index","adapter":"portal_bridge","originChainId":23}
base mint burn via portal_bridge
5
0x9af6c42076cf1c54752cb628d6ce235e2d71814dsame open
illiquidpools hold $1, under the floor

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

discord+2{"notes":["**Wormhole NTT**"],"proven":true,"ticker":"NTT","source_tx":"0x55d0bd6b2d068dfd4e89336b11e59f315f6d25906be9db4101bf399366b3b528","message_id":"1393550412069736511","message_ts":"2025-07-12T11:11:49","source_url":"https://wormholescan.io/#/tx/0x55d0bd6b2d068dfd4e89336b11e59f315f6d25906be9db4101bf399366b3b528?network=Mainnet","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1393550412069736511","source_kind":"wormhole_tx","curator_liquidity":false}
same_address+3{"chain":"base"}

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 arbitrum 1 of 1 reachable
base portal_bridge 0x55d0bd6b… 21 h ago
from base 1 of 1 reachable
arbitrum portal_bridge 0x715528e6… 21 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9310 21 h ago portal_bridgearbitrum → base 0x55d0bd6b…b3b528 DISCOVERED 9 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.