Token Dashboard
tokens
1962
contracts
6141
confirmed
5689 of 6141
chains seen
14
unmeasured
181
queued
0

NFD

Feisty Doge
status
fully reported3/3 checked · 3 liquid · 3 reported · hot
first bridged
2 d ago
arrived via
base_bridge
contracts
4 on 3 chains
confirmed by a transfer
4 of 4
liquidity
3 of 3 chains checked · 3 liquid
checking
hot
already alerted on
ethereum, solana, base
pins
3

Lifecycle

  1. first pin received 2026-09-03 06:06:14 UTC · 2 d ago #6470 via base_bridge
  2. token discovered 2026-09-03 08:06:23 UTC · 2 d ago 4 contracts today
  3. first liquid 2026-09-04 17:03:50 UTC · 7 h ago a chain quoted liquid
  4. first alert 2026-09-04 06:15:10 UTC · 18 h ago multi_chain_liquid, sent 18 h ago
  5. reported chains ethereum, solana, base — 3 of 3

Where this token lives

More than one contract on base (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.

base mint burn via base_bridge 8
0x37289326b7bca5a776a5071b8d693c0588c5c9a6 open
liquidlast verified 7 h ago

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

registry+3{"tx":"0xe6aebe601e1489981d5d47ab2468e800b917326058abf69e294036f042c55776","from":"bridge_pin"}
derivation+5{"via":"remoteToken","adapter":"base_bridge"}
ethereum canonical via portal_bridge 13
0xdfdb7f72c1f195c5951a234e8db9806eb0635346 open
liquidlast verified 7 h ago

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

derivation+5{"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0x37289326b7bca5a776a5071b8d693c0588c5c9a6"}
registry+3{"tx":"0x84274eb451443013c1e156589e76ef851e1a5cf859e2c2a3a76b7c267cc19258","from":"bridge_pin"}
derivation+5{"via":"origin_from_index","adapter":"portal_bridge","originChainId":2}
base mint burn via base_bridge shadowed · not checked 5
0x117cfd9060525452db4a34d51c0b3b7599087f05 open
liquidlast verified 20 h ago

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

bridge_transfer+5{"tx":"0x64c70ef0dc86ed0abfede378f5f8cdac0a1c092b3a4622c5638b7774d6741c09","adapter":"base_bridge"}
solana lock mint wrapper via portal_bridge decimals differ from source 5
CY2E69dSG9vBsMoaXDvYmMDSMEP4SZtRY1rqVQ9tkNDu open
liquidlast verified 7 h ago

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

derivation+5{"via":"wrapped_mint_pda","adapter":"portal_bridge","originChainId":2}

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 base 1 of 2 reachable
ethereum base_bridge 0xe6aebe60… 2 d ago
show 1 unreachable hide unreachable
solana no transfer seen
from ethereum 2 of 2 reachable
base base_bridge 0xb85548b3… 2 d ago
solana portal_bridge 0x84274eb4… 2 d ago
from solana 1 of 2 reachable
ethereum portal_bridge 3JoqNiA8je… 2 d ago
show 1 unreachable hide unreachable
base no transfer seen

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#7027 2 d ago portal_bridgeethereum → solana 0x84274eb4…c19258 DISCOVERED 3 h 45 min
#7026 2 d ago base_bridgeethereum → base 0xfa87af24…e66393 SKIPPED_DUPLICATE 3 h 44 min
#6470 2 d ago base_bridgebase → ethereum 0xe6aebe60…c55776 DISCOVERED 2 h

Alerts

KindCreatedStateSentTelegram id
chain_added7 h ago SENT 7 h ago778
multi_chain_liquid18 h ago SENT 18 h ago580

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.