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

SFI

Spice
status
partly reported4/4 checked · 3 liquid · 3 reported · hot
first bridged
3 d ago
arrived via
robinhood_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
arbitrum, ethereum, polygon
pins
3

Lifecycle

  1. first pin received 2026-09-03 04:01:23 UTC · 2 d ago #5669 via polygon_bridge
  2. token discovered 2026-09-02 05:03:03 UTC · 3 d ago 4 contracts today
  3. first liquid 2026-09-04 05:54:35 UTC · 18 h ago a chain quoted liquid
  4. first alert 2026-09-04 05:54:35 UTC · 18 h ago multi_chain_liquid, sent 18 h ago
  5. reported chains arbitrum, ethereum, polygon — 3 of 4

Where this token lives

ethereum canonical via arbitrum_bridge 24
0xb753428af26e81097e7fd17f40c88aaa3e04902c open
liquidlast verified 18 h ago

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

registry+3{"tx":"0xbed1758377437d99b75a625569843cf18a73b10029a3db2a88ec3262ec9548b3","from":"bridge_pin"}
derivation+5{"via":"pin_source","adapter":"robinhood_bridge"}
registry+3{"tx":"0xfef8c0f2b42645afe0b6a6f11fee1646ba24b7384e55ebdc2a1ca7e402b981e2","from":"bridge_pin"}
derivation+5{"via":"pin_source","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}
registry+3{"tx":"0x16c82f21fc56d3a68646ec42bbe2cf978d8ad19474e0cc9c30fe41ffe2e59629","from":"bridge_pin"}
derivation+5{"via":"pin_source","adapter":"arbitrum_bridge"}
robinhood mint burn via robinhood_bridge 5
0xe77d354898a44808ff3999947002785cd727bed5 open
illiquidno route found

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

derivation+5{"via":"calculateL2TokenAddress","router":"0x6a2e3a1e16fc29f27ce61429746d558d656975bb","adapter":"robinhood_bridge"}
polygon mint burn via polygon_bridge 5
0x35b937583f04a24963eb685f728a542240f28dd8 open
liquidlast verified 18 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
0xff0490bf1a58a4151d4d6ec6cb3d2959a561874c open
liquidlast verified 18 h ago

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
ethereum no transfer seen
polygon no transfer seen
robinhood no transfer seen
from ethereum 3 of 3 reachable
arbitrum arbitrum_bridge 0x16c82f21… 28 h ago
polygon polygon_bridge 0xfef8c0f2… 28 h ago
robinhood robinhood_bridge 0xbed17583… 3 d ago
from polygon 0 of 3 reachable

No transfer has been seen leaving polygon.

show 3 unreachable hide unreachable
arbitrum no transfer seen
ethereum no transfer seen
robinhood no transfer seen
from robinhood 0 of 3 reachable

No transfer has been seen leaving robinhood.

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

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8379 2 d ago polygon_bridgeethereum → polygon 0x1d41d213…cda30c SKIPPED_DUPLICATE 13 h
#8378 2 d ago arbitrum_bridgeethereum → arbitrum 0x16c82f21…e59629 DISCOVERED 13 h
#5669 2 d ago polygon_bridgeethereum → polygon 0xfef8c0f2…b981e2 DISCOVERED 2 h

Alerts

KindCreatedStateSentTelegram id
multi_chain_liquid18 h ago SENT 18 h ago509

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.