Srey0x

Srey0x Apex

status: unmeasured2/2 checked · 0 liquid · warm
first bridged: 2 d ago
arrived via: axelar
contracts: 2 on 2 chains
confirmed by a transfer: 2 of 2
liquidity: 2 of 2 chains checked · 0 liquid · 1 unmeasured
checking: warm
already alerted on: nothing yet
pins: 2

Lifecycle

first pin received 2026-09-03 06:06:14 UTC · 2 d ago #6527 via axelar
token discovered 2026-09-03 08:15:31 UTC · 2 d ago 2 contracts today
first liquid pending not yet
first alert pending not yet
reported chains pending none yet

Where this token lives

ethereum mint burn via axelar 5

0xce0c98581168fdb1f5b867a71c9a8ac6281ee6b0 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

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

base canonical via axelar 3

0x4b47be6cf6438fcce3f5fc150618c4eea12e5cd1 open

unknownBALANCE_READ_FAILED — not a negative result

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

registry

{"tx":"0xcee0ffedab9348bf43315a8bd8b2bfd5abf633657c235c6b0c6c9694eb8dcdad","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 0x616ff00e… 2 d ago

from ethereum 1 of 1 reachable

base axelar 0xbc4a4324… 35 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#6968	2 d ago	axelarethereum → base	0x650816a9…dcfcba	SKIPPED_DUPLICATE	3 h 35 min
#6527	2 d ago	axelarbase → ethereum	0xcee0ffed…8dcdad	DISCOVERED	2 h 9 min

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