Token Dashboard
tokens
1959
contracts
6132
confirmed
5681 of 6132
chains seen
14
unmeasured
171
queued
0

EV

Everything
status
partly reported4/4 checked · 2 liquid · 2 reported · hot
first bridged
2 d ago
arrived via
portal_bridge
contracts
5 on 4 chains
confirmed by a transfer
5 of 5
liquidity
4 of 4 chains checked · 2 liquid
checking
hot
already alerted on
binance, ethereum
pins
5

Lifecycle

  1. first pin received 2026-09-02 22:30:57 UTC · 2 d ago #3333 via portal_bridge
  2. token discovered 2026-09-02 22:18:32 UTC · 2 d ago 5 contracts today
  3. first liquid 2026-09-04 06:50:12 UTC · 13 h ago a chain quoted liquid
  4. first alert 2026-09-04 06:50:12 UTC · 13 h ago multi_chain_liquid, sent 13 h ago
  5. reported chains binance, ethereum — 2 of 4

Where this token lives

More than one contract on arbitrum (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 arbitrum_bridge 16
0xe7e7e741c23a4767831a56a8c99f522c5ac1e7e7same open
liquidlast verified 13 h ago

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

registry+3{"tx":"0xc324ec77a914077a8762a883012dd23ab9bba7d60930cf37623c75827eebf8e5","from":"bridge_pin"}
derivation+5{"via":"origin_from_index","adapter":"portal_bridge","originChainId":2}
registry+3{"tx":"0x0c1daf07cb12eca594bc92f02827e2d1c7355181d09bd42d002a97031a01e794","from":"bridge_pin"}
derivation+5{"via":"pin_source","adapter":"arbitrum_bridge"}
binance mint burn via portal_bridge 10
0xe7e7e741c23a4767831a56a8c99f522c5ac1e7e7same open
liquidlast verified 13 h ago

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

same_address+3{"chain":"binance"}
codehash+2{"codehash":"0xf15713b6ec467ae86c9194f3217d8d94360edb17eeca7e6d57c7fdb9e9c730de"}
derivation+5{"via":"ntt_peer","adapter":"portal_bridge","manager":"0xf432b2564cc0e233482a1f2af0eda4832cf435cd","wormholeId":4,"peerManager":"0xf432b2564cc0e233482a1f2af0eda4832cf435cd"}
base mint burn via portal_bridge 10
0xe7e7e741c23a4767831a56a8c99f522c5ac1e7e7same open
illiquidpools hold $0, under the floor

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

same_address+3{"chain":"base"}
codehash+2{"codehash":"0xf15713b6ec467ae86c9194f3217d8d94360edb17eeca7e6d57c7fdb9e9c730de"}
derivation+5{"via":"ntt_peer","adapter":"portal_bridge","manager":"0xf432b2564cc0e233482a1f2af0eda4832cf435cd","wormholeId":30,"peerManager":"0x0581b84e13f88830feb288236fa1ab08c9c1cd91"}
arbitrum mint burn via portal_bridge 10
0xe7e7e741c23a4767831a56a8c99f522c5ac1e7e7same open
illiquidpools hold $0, under the floor

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

same_address+3{"chain":"arbitrum"}
codehash+2{"codehash":"0xf15713b6ec467ae86c9194f3217d8d94360edb17eeca7e6d57c7fdb9e9c730de"}
derivation+5{"via":"ntt_peer","adapter":"portal_bridge","manager":"0xf432b2564cc0e233482a1f2af0eda4832cf435cd","wormholeId":23,"peerManager":"0xf432b2564cc0e233482a1f2af0eda4832cf435cd"}
arbitrum mint burn via arbitrum_bridge shadowed · not checked 5
0x37058c4b45fdfc8953fb453da4d6d83670ecdf9d open
illiquidpools hold $0, under the floor

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

derivation+5{"via":"calculateL2TokenAddress","router":"0x72ce9c846789fdb6fc1f34ac4ad25dd9ef7031ef","adapter":"arbitrum_bridge"}

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 arbitrum 3 of 3 reachable
base portal_bridge 0x4a935d78… 2 d ago
binance portal_bridge 0xd0951ba8… 2 d ago
ethereum portal_bridge 0x32e76a38… 24 h ago
from base 3 of 3 reachable
arbitrum portal_bridge 0x58d29aed… 2 d ago
binance portal_bridge 0x37500d2d… 2 d ago
ethereum portal_bridge 0x2a115121… 2 d ago
from binance 3 of 3 reachable
arbitrum portal_bridge 0x4c86fb72… 24 h ago
base portal_bridge 0x6ae028ba… 2 d ago
ethereum portal_bridge 0x56521f69… 2 d ago
from ethereum 3 of 3 reachable
arbitrum portal_bridge, arbitrum_bridge 0xda1ccf07… 21 h ago
base portal_bridge 0x74c3e517… 2 d ago
binance portal_bridge 0xc324ec77… 2 d ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9094 28 h ago arbitrum_bridgeethereum → arbitrum 0x0c1daf07…01e794 DISCOVERED 6 h
#8434 2 d ago portal_bridgeethereum → arbitrum 0xbb288615…e01296 SKIPPED_DUPLICATE 13 h
#8433 2 d ago portal_bridgebinance → arbitrum 0x143c9648…9beb43 SKIPPED_DUPLICATE 13 h
#8432 2 d ago portal_bridgearbitrum → ethereum 0xf74fac4b…2d0713 SKIPPED_DUPLICATE 13 h
#3333 2 d ago portal_bridgeethereum → arbitrum 0xe203e9cc…063a35 SKIPPED_DUPLICATE 5 h 45 min

Alerts

KindCreatedStateSentTelegram id
multi_chain_liquid13 h ago SENT 13 h ago705

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.