Token Dashboard
tokens
2812
contracts
8315
confirmed
5693 of 8315
chains seen
14
unmeasured
175
queued
0

TEL

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

Lifecycle

  1. first pin received 2026-09-02 23:56:14 UTC · 2 d ago #3986 via polygon_bridge
  2. token discovered 2026-09-03 02:16:48 UTC · 2 d ago 4 contracts today
  3. first liquid 2026-09-04 05:07:18 UTC · 21 h ago a chain quoted liquid
  4. first alert 2026-09-04 05:07:18 UTC · 21 h ago multi_chain_liquid, sent 21 h ago
  5. reported chains base, ethereum, polygon — 3 of 4

Where this token lives

ethereum canonical via arbitrum_bridge 21
0x467bccd9d29f223bce8043b84e8c8b282827790f open
liquidlast verified 21 h ago

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

registry+3{"tx":"0xdcdfd742fc938aadaa10459700e2e516b12274f5ebe6ec75bb1805b5f5fc6b22","from":"bridge_pin"}
derivation+5{"via":"pin_source","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}
derivation+5{"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0x09be1692ca16e06f536f0038ff11d1da8524adb1"}
registry+3{"tx":"0x53d1f6f327c43abe639bf296206ba59e7081cbd53e2373aed586dce5fe3dca2b","from":"bridge_pin"}
derivation+5{"via":"pin_source","adapter":"arbitrum_bridge"}
base mint burn via base_bridge 8
0x09be1692ca16e06f536f0038ff11d1da8524adb1 open
liquidlast verified 21 h ago

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

registry+3{"tx":"0x1f98640b19c8d8fd36b2c1c8c3cd3cfafab2a325fc1f17d55b48ba9870f29c1a","from":"bridge_pin"}
derivation+5{"via":"remoteToken","adapter":"base_bridge"}
polygon mint burn via polygon_bridge 5
0xdf7837de1f2fa4631d716cf2502f8b230f1dcc32 open
liquidlast verified 21 h ago

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

derivation+5{"via":"rootToChildToken","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}
arbitrum mint burn via arbitrum_bridge 5
0x0419e8bfbbb2623728c3a6129090da4ff4e48113 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 0 of 3 reachable

No transfer has been seen leaving arbitrum.

show 3 unreachable hide unreachable
base no transfer seen
ethereum no transfer seen
polygon no transfer seen
from base 1 of 3 reachable
ethereum base_bridge 0x1f98640b… 2 d ago
show 2 unreachable hide unreachable
arbitrum no transfer seen
polygon no transfer seen
from ethereum 3 of 3 reachable
arbitrum arbitrum_bridge 0x53d1f6f3… 34 h ago
base base_bridge 0xa3dfdb07… 32 h ago
polygon polygon_bridge 0xdcdfd742… 32 h ago
from polygon 0 of 3 reachable

No transfer has been seen leaving polygon.

show 3 unreachable hide unreachable
arbitrum no transfer seen
base no transfer seen
ethereum no transfer seen

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8258 2 d ago polygon_bridgeethereum → polygon 0xe5f07008…c487c3 SKIPPED_DUPLICATE 11 h
#8257 2 d ago base_bridgeethereum → base 0x7362f36d…c915a7 SKIPPED_DUPLICATE 11 h
#7431 2 d ago arbitrum_bridgeethereum → arbitrum 0x53d1f6f3…3dca2b DISCOVERED 9 h
#7207 2 d ago base_bridgebase → ethereum 0x1f98640b…f29c1a DISCOVERED 4 h 5 min
#3986 2 d ago polygon_bridgeethereum → polygon 0x5dc52456…907b8c SKIPPED_DUPLICATE 4 h 46 min

Alerts

KindCreatedStateSentTelegram id
multi_chain_liquid21 h ago SENT 21 h ago325

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.