DRAGONX

DragonX

status: fully reported2/2 checked · 2 liquid · 2 reported · hot
first bridged: 34 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: 2

Lifecycle

first pin received 2026-09-03 06:06:18 UTC · 2 d ago #6896 via axelar
token discovered 2026-09-03 09:30:05 UTC · 34 h ago 2 contracts today
first liquid 2026-09-04 05:39:25 UTC · 13 h ago a chain quoted liquid
first alert 2026-09-04 05:39:25 UTC · 13 h ago multi_chain_liquid, sent 13 h ago
reported chains base, ethereum — 2 of 2

Where this token lives

ethereum mint burn via axelar 5

0x96a5399d07896f757bd4c6ef56461f58db951862 open

liquidlast verified 13 h ago

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

bridge_transfer

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

base canonical via axelar 3

0xb7a591424b363ac06379396ff9c8c5439e3eac33 open

liquidlast verified 14 h ago

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

registry

{"tx":"0xdc4d67fc76ca281e93faad4414a4d6db997253c4a0db23e896f582ca5777beb4","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 0x54704591… 34 h ago

from ethereum 1 of 1 reachable

base axelar 0x5ad9b5c4… 26 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7723	2 d ago	axelarethereum → base	0x25e332bc…3ee7df	SKIPPED_DUPLICATE	10 h
#6896	2 d ago	axelarbase → ethereum	0xdc4d67fc…77beb4	DISCOVERED	3 h 24 min

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	13 h ago	SENT	13 h ago	443

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