XCHNG

Chainge

status: illiquid2/2 checked · 0 liquid · warm
first bridged: 36 h ago
arrived via: arbitrum_bridge
contracts: 2 on 2 chains
confirmed by a transfer: 2 of 2
liquidity: 2 of 2 chains checked · 0 liquid
checking: warm
already alerted on: nothing yet
pins: 1

Lifecycle

first pin received 2026-09-03 06:06:43 UTC · 2 d ago #7826 via arbitrum_bridge
token discovered 2026-09-03 16:53:18 UTC · 36 h ago 2 contracts today
first liquid pending not yet
first alert pending not yet
reported chains pending none yet

Where this token lives

ethereum canonical via arbitrum_bridge 8

0xb712d62fe84258292d1961b5150a19bc4ab49026 open

illiquidpools hold $0, under the floor

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

registry	+3	{"tx":"0xba5d64a82ae46fb0d8100e9bffe9d15976de77c52ef05b29b3375f403dc2c1f1","from":"bridge_pin"}
derivation	+5	{"via":"pin_source","adapter":"arbitrum_bridge"}

arbitrum mint burn via arbitrum_bridge 5

0x51c601dc278eb2cfea8e52c4caa35b3d6a9a2c26 open

illiquidpools hold $0, under the floor

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

derivation

{"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 1 reachable

No transfer has been seen leaving arbitrum.

show 1 unreachable hide unreachable

ethereum no transfer seen

from ethereum 1 of 1 reachable

arbitrum arbitrum_bridge 0xba5d64a8… 36 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7826	2 d ago	arbitrum_bridgeethereum → arbitrum	0xba5d64a8…c2c1f1	DISCOVERED	10 h

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