RLC

iEx.ec Network Token

status: fully reported2/2 checked · 2 liquid · 2 reported · hot
first bridged: 2 d ago
arrived via: layerzero
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: arbitrum, ethereum
pins: 1

Lifecycle

first pin received 2026-09-03 06:06:41 UTC · 2 d ago #7522 via layerzero
token discovered 2026-09-03 01:38:16 UTC · 2 d ago 2 contracts today
first liquid 2026-09-04 08:09:23 UTC · 21 h ago a chain quoted liquid
first alert 2026-09-04 08:09:23 UTC · 21 h ago multi_chain_liquid, sent 21 h ago
reported chains arbitrum, ethereum — 2 of 2

Where this token lives

ethereum mint burn via layerzero 5

0x607f4c5bb672230e8672085532f7e901544a7375 open

liquidlast verified 21 h ago

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

bridge_transfer

{"tx":"0xe1fe32c11f77311c29b0b0b4597827b236cec3e61abff7c2b38cad476538ec21","adapter":"layerzero"}

arbitrum canonical via layerzero 3

0xe649e6a1f2afc63ca268c2363691cecaf75cf47c open

liquidlast verified 21 h ago

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

registry

{"tx":"0xe1fe32c11f77311c29b0b0b4597827b236cec3e61abff7c2b38cad476538ec21","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 arbitrum 1 of 1 reachable

ethereum layerzero 0xe1fe32c1… 2 d ago

from ethereum 1 of 1 reachable

arbitrum layerzero 0x4451202f… 2 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7522	2 d ago	layerzeroethereum → arbitrum	0xaf87bb5e…f57417	SKIPPED_DUPLICATE	10 h

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	21 h ago	SENT	21 h ago	723

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