AZUR
Azuro
status fully reported 2/2 checked · 2 liquid · 2 reported · hot
first bridged 2 d ago
arrived via base_bridge
contracts 2 on 2 chains
confirmed by a transfer 2 of 2
liquidity 2 of 2 chains checked · 2 liquid
checking hot
already alerted on base, ethereum
Lifecycle
first pin received
2026-09-03 00:19:29 UTC · 2 d ago
#4055 via base_bridge
token discovered
2026-09-02 20:56:15 UTC · 2 d ago
2 contracts today
first liquid
2026-09-03 22:07:53 UTC · 20 h ago
a chain quoted liquid
first alert
2026-09-03 22:07:53 UTC · 20 h ago
multi_chain_liquid, sent 20 h ago
reported chains
base, ethereum — 2 of 2
Where this token lives
base
canonical
via portal_bridge
16
0x2b4d0fc2294aa9686adf6c5a7ba25f66dccdf6c0
copy
open
liquid last verified 20 h ago
4 of 4 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0x43f6b53de2e7ed2f553afa5a59156a8ecef4621d396e9ea256ef98d5d41ad3ec","from":"bridge_pin"} derivation +5 {"via":"remoteToken","adapter":"base_bridge"} registry +3 {"tx":"0x012bf9451eef1fc47bffecef791e044c5c9a72d41f6df4a2dbb02cb2eb2328e8","from":"bridge_pin"} derivation +5 {"via":"origin_from_index","adapter":"portal_bridge","originChainId":30}
ethereum
canonical
via base_bridge
5
0x9e6be44cc1236eef7e1f197418592d363bedcd5a
copy
open
liquid last verified 20 h ago
1 of 1 sources are protocol-attested — a contract confirmed this link.
derivation +5 {"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0x2b4d0fc2294aa9686adf6c5a7ba25f66dccdf6c0"}
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
1 of 1 reachable
→
ethereum
base_bridge, portal_bridge
0x012bf945…
3 h ago
from ethereum
1 of 1 reachable
Pins behind this token
Alerts
Kind Created State Sent Telegram id
multi_chain_liquid 20 h ago
SENT 20 h ago 300