LEPO (SLAY)
name unknown
status illiquid 2/2 checked · 0 liquid · warm
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 warm
already alerted on nothing yet
Lifecycle
first pin received
2026-09-06 13:59:36 UTC · 20 h ago
#9332 via layerzero
token discovered
2026-09-05 12:33:06 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
canonical
via layerzero
decimals differ from source
6
0xbe9cf7e1603dee2494bec965f345cb728485f33c
copy
open
illiquid pools hold $0, under the floor
1 of 2 sources are protocol-attested — a contract confirmed this link.
discord +1 {"notes":[],"proven":false,"ticker":"LEPO (SLAY)","source_tx":null,"message_id":"1402910434599768095","message_ts":"2025-08-07T07:05:12","source_url":"https://layerzeroscan.com/address/0xca2C7cffca0BF38639e689549874F4072C0A95DB","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1402910434599768095","source_kind":"oft_address","curator_liquidity":false} peer_map +5 {"via":{"address":"0x5ae715b48be7474ed0246eeab87d93c262817c54","chainSlug":"binance"},"adapter":"layerzero","oftAdapter":"0xca2c7cffca0bf38639e689549874f4072c0a95db","unwrappedTo":"0xbe9cf7e1603dee2494bec965f345cb728485f33c"}
binance
canonical
via layerzero
4
0x5ae715b48be7474ed0246eeab87d93c262817c54
copy
open
illiquid pools hold $0, under the floor
1 of 2 sources are protocol-attested — a contract confirmed this link.
discord +1 {"notes":[],"proven":false,"ticker":"LEPO (SLAY)","source_tx":null,"message_id":"1402910434599768095","message_ts":"2025-08-07T07:05:12","source_url":"https://layerzeroscan.com/address/0xca2C7cffca0BF38639e689549874F4072C0A95DB","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1402910434599768095","source_kind":"oft_address","curator_liquidity":false} registry +3 {"tx":"0xe44a32228a9d7ff389e27e16bd4d5b4745f24071f932017d75840b5734669bf9","from":"bridge_pin"}
How it moves between chains
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.
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 binance
1 of 1 reachable
from ethereum
1 of 1 reachable
Pins behind this token
Pin Received Bridge Bridge tx Outcome Discovery took
#9332 20 h ago
layerzerobinance → ethereum
0xe44a3222…669bf9 DISCOVERED
11 min
Verdict. Add it if this is the token you want to watch; reject it if any contract is a twin, a clone or junk — a rejected token stays checked but is not alerted on again.