HOKK

Hokkaidu Inu

status: fully reported2/2 checked · 2 liquid · 2 reported · hot
first bridged: 14 h ago
arrived via: axelar
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
pins: 1

Lifecycle

first pin received 2026-09-04 02:27:14 UTC · 14 h ago #9132 via axelar
token discovered 2026-09-04 02:27:42 UTC · 14 h ago 2 contracts today
first liquid 2026-09-04 04:11:32 UTC · 12 h ago a chain quoted liquid
first alert 2026-09-04 04:11:32 UTC · 12 h ago multi_chain_liquid, sent 12 h ago
reported chains base, ethereum — 2 of 2

Where this token lives

ethereum mint burn via axelar 5

0xc40af1e4fecfa05ce6bab79dcd8b373d2e436c4e open

liquidlast verified 12 h ago

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

bridge_transfer

{"tx":"0x031201f1b8e866c4df71386909c1eeba17293fb1b48a4d78c294fa58c9014270","adapter":"axelar"}

base canonical via axelar 3

0xd857af86a2c5b4f46fc7cb8032bd4f5625577eeb open

liquidlast verified 12 h ago

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

registry

{"tx":"0x0ec06031434efc33ad1ee2a31a624c90e80dae45a1f7da1dee5d91254cf2b8fd","from":"bridge_pin"}

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 axelar 0x031201f1… 14 h ago

from ethereum 1 of 1 reachable

base axelar 0xfcf1e31d… 14 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#9132	14 h ago	axelarbase → ethereum	0x0ec06031…f2b8fd	DISCOVERED	28 s

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	12 h ago	SENT	12 h ago	317

Every address above came from an on-chain read. The evidence trail shows which read produced it.