Token Dashboard
tokens
2787
contracts
8387
confirmed
5820 of 8387
chains seen
14
unmeasured
147
queued
0

DIMO

Dimo
status
liquid2/2 checked · 1 liquid · warm
first bridged
3 d ago
arrived via
base_bridge
contracts
3 on 2 chains
confirmed by a transfer
3 of 3
liquidity
2 of 2 chains checked · 1 liquid
checking
warm
already alerted on
nothing yet
pins
0

Lifecycle

  1. first pin received pending no pin linked (added by hand, or before pins were tracked)
  2. token discovered 2026-09-02 22:25:50 UTC · 3 d ago 3 contracts today
  3. first liquid 2026-09-06 05:17:33 UTC · 4 min ago a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

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.

ethereum canonical via base_bridge 8
0x5fab9761d60419c9eeebe3915a8fa1ed7e8d2e1b open
liquid206 bps · 2.06% via kyberswap

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

registry+3{"tx":"0xa16f131b391306a13274731890eeb611ffc14c10233efcefa4abde779557f19c","from":"bridge_pin"}
derivation+5{"via":"pin_source","adapter":"base_bridge"}
base mint burn via base_bridge 5
0xd7ea8433b434223b3da2931620391df157d1c22d open
illiquidpools hold $0, under the floor

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

bridge_transfer+5{"tx":"0x281927838843a30d9d06c97f1da808442a113b6a38d09f1994521fd0afbc69f4","adapter":"base_bridge"}
base mint burn via base_bridge shadowed · not checked 7
0x5eaa326fb2fc97facce6a79a304876dad0f2e96c open
illiquidpools hold $0, under the floor

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

bridge_transfer+5{"tx":"0xf6657049fc163206828cc741c7ed9b46555cf73a86592f8b0f06b9780be2dac0","adapter":"base_bridge"}
discord+2{"notes":["Wormhole NTT"],"proven":true,"ticker":"DIMO","source_tx":"0xe06ac2ccb6cd8b3972b3af6fb2d93ce00ee208c564eef3ebea3fb780228c34ff","message_id":"1383202922107502742","message_ts":"2025-06-13T21:54:35","source_url":"https://wormholescan.io/#/tx/0xe06ac2ccb6cd8b3972b3af6fb2d93ce00ee208c564eef3ebea3fb780228c34ff?network=Mainnet","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1383202922107502742","source_kind":"wormhole_tx","curator_liquidity":false}

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 0 of 1 reachable

No transfer has been seen leaving base.

show 1 unreachable hide unreachable
ethereum no transfer seen
from ethereum 1 of 1 reachable
base base_bridge 0xf6657049… 3 d ago

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.