HEAT

status: illiquid2/2 checked · 0 liquid · cold
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 · 0 liquid
checking: cold
already alerted on: nothing yet
pins: 2

Lifecycle

first pin received 2026-09-03 06:06:40 UTC · 2 d ago #7395 via layerzero
token discovered 2026-09-03 15:54:58 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

base mint burn via layerzero 5

0xa136e8e8ff4294b4df056c7e0a8a3655c6e9ed83 open

illiquidpools hold $0, under the floor

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

peer_map

{"via":{"address":"0x39fa5d13f0a46872c42333699209cd172f7e5bd4","chainSlug":"arbitrum"},"adapter":"layerzero"}

arbitrum canonical via layerzero 3

0x39fa5d13f0a46872c42333699209cd172f7e5bd4 open

illiquidpools hold $0, under the floor

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

registry

{"tx":"0xc045543f200351080301dae1b41220d65bbac18f7401fd90e835527a58f4eb5b","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

base layerzero 0xc045543f… 2 d ago

from base 1 of 1 reachable

arbitrum layerzero 0x0910fbd9… 2 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7750	2 d ago	layerzerobase → arbitrum	0x0910fbd9…a0191a	SKIPPED_DUPLICATE	10 h
#7395	2 d ago	layerzeroarbitrum → base	0xc045543f…f4eb5b	DISCOVERED	9 h

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