Token Dashboard
tokens
2787
contracts
8841
confirmed
7197 of 8841
chains seen
14
unmeasured
97
queued
0

MGT

name unknown
status
liquid2/2 checked · 1 liquid · 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 · 1 liquid
checking
hot
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-06 13:56:53 UTC · 17 h ago #9261 via layerzero
  2. token discovered 2026-09-05 12:33:06 UTC · 2 d ago 2 contracts today
  3. first liquid 2026-09-07 07:16:34 UTC · just now a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

binance canonical via layerzero
6
0x3c6256f234ba638e5883c46b3fedb00ea2e66b8a open
liquid374 bps · 3.74% via kyberswap

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

discord+1{"notes":[],"proven":false,"ticker":"MGT","source_tx":null,"message_id":"1371825501080915988","message_ts":"2025-05-13T12:24:46","source_url":"https://layerzeroscan.com/address/0x08BF7F2005Ab25A90d4f88eFd70Dbdf0EF6B7554","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1371825501080915988","source_kind":"oft_address","curator_liquidity":true}
peer_map+5{"via":{"address":"0x08bf7f2005ab25a90d4f88efd70dbdf0ef6b7554","chainSlug":"base"},"adapter":"layerzero","oftAdapter":"0x08bf7f2005ab25a90d4f88efd70dbdf0ef6b7554","unwrappedTo":"0x3c6256f234ba638e5883c46b3fedb00ea2e66b8a"}
base canonical via layerzero
4
0x08bf7f2005ab25a90d4f88efd70dbdf0ef6b7554 open
illiquidpools hold $0, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"MGT","source_tx":null,"message_id":"1371825501080915988","message_ts":"2025-05-13T12:24:46","source_url":"https://layerzeroscan.com/address/0x08BF7F2005Ab25A90d4f88eFd70Dbdf0EF6B7554","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1371825501080915988","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0xd2805a353aec09e282575be865d6c01f8e2bf5eb9de0903d347f288b0f03f2f5","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 base 1 of 1 reachable
binance layerzero 0xd2805a35… 17 h ago
from binance 1 of 1 reachable
base layerzero 0x24c3f76e… 17 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9261 17 h ago layerzerobase → binance 0xd2805a35…03f2f5 DISCOVERED 1 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.

Exclude this token if it is junk or not worth watching. Liquidity stops being checked and nothing more is searched for it; its contracts, evidence, routes and history stay, its pins are still recorded, and it can be tracked again from the Excluded page.

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