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

AIKEK

AlphaKEK.AI
status
fully reported3/3 checked · 3 liquid · 3 reported · hot
first bridged
3 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
base, ethereum, solana
pins
1

Lifecycle

  1. first pin received 2026-09-03 06:06:42 UTC · 2 d ago #7689 via portal_bridge
  2. token discovered 2026-09-02 04:25:00 UTC · 3 d ago 4 contracts today
  3. first liquid 2026-09-04 05:19:08 UTC · 16 h ago a chain quoted liquid
  4. first alert 2026-09-04 05:19:08 UTC · 16 h ago multi_chain_liquid, sent 16 h ago
  5. reported chains base, ethereum, solana — 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
0x681a09a902d9c7445b3b1ab282c38d60c72f1f09 open
liquidlast verified 16 h ago

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

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

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

derivation+5{"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0x681a09a902d9c7445b3b1ab282c38d60c72f1f09"}
registry+3{"tx":"0x8bc56a0081cdfdf26de9f084a92c5dfd9538cf1d15512d97d07d310b724045fa","from":"bridge_pin"}
derivation+5{"via":"origin_from_index","adapter":"portal_bridge","originChainId":2}
base lock mint wrapper via portal_bridge shadowed · not checked 5
0xb929863c9b61e34f1b414269b955e8c3b3e3873f open
liquidlast verified 18 h ago

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

derivation+5{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0x8d2de8d2f73F1F4cAB472AC9A881C9b123C79627","originChainId":2}
solana lock mint wrapper via portal_bridge decimals differ from source 5
CotWkXoBD3edLb6opEGHV9tb3pyKmeoWBLwdMJ8ZDimW open
liquidlast verified 16 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 2 of 2 reachable
ethereum base_bridge, portal_bridge 0xbbbdaef7… 29 h ago
solana portal_bridge 0xd50075b3… 29 h ago
from ethereum 2 of 2 reachable
base base_bridge, portal_bridge 0xb3e8e679… 29 h ago
solana portal_bridge 0x8bc56a00… 29 h ago
from solana 2 of 2 reachable
base portal_bridge 2kmXo2ykDj… 29 h ago
ethereum portal_bridge 3YVvGw7jEK… 29 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#7689 2 d ago portal_bridgeethereum → solana 0x8bc56a00…4045fa DISCOVERED 10 h

Alerts

KindCreatedStateSentTelegram id
multi_chain_liquid16 h ago SENT 16 h ago365

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.