XSCAPE
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
noteThe creator sold while we were watching.
noteOnly 7.1 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 00:23 UTC |
| Creator | 9vY3HLn2sZ6pVDqECoRq3QyQ4ozaZYw7FRfAz3Wp79NC |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 415 distinct wallets, not counting the creator, bought on the bonding curve: 79 within the first 30s, 11 bundled into the creation block. |
| Graduated | 5 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.3 days ago and it was finished. Checked 2026-09-30 00:32 UTC. |
| Creator sold | yes |
| Recorded from | Kzvj6T4AXSZxcSHzuycykd… slot 451,801,763
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 00:23:20 UTC Slot 451,801,763, which is the chain's own clock for this moment. |
| Creation block | 11 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 79 distinct buyers, within the first thirty seconds. A snapshot taken off a tick at the thirty-second mark, so
it carries no moment of its own; it is placed here because that is where it happened. |
| Curve completed | 2026-09-30 00:28:13 UTC +4m 53s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-30 00:28:13 UTC +4m 53s
4.109e-7 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.
Seen before
| This picture | On 31 launches from 31 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 37 launches from 37 creator wallets, including this one. See them → |
Pool
| Liquidity | 7.1 SOL |
| Read from chain | 2026-10-01 08:35 UTC, just now |
What this launch claimed to be
| Name | XSCAPE |
| Description | $XSCAPE drops you into Andromeda with one job: survive long enough to find a way home 🚀 Choose Breacher, Ranger, or Technician, scavenge hostile sectors, rebuild navigation, and upgrade your habitat. |
| Metadata held | sha256 80b926fe26b9b338ffd4a2072b23decb05be2d5d3db4d50781814a61beb01cba · 589 bytes Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-10-01 00:23 UTC. |
| Picture held | sha256 f5cd667a4c080c009e32b6182088b832f26485c3a87eb4c61ef249b7a8a35e27 · 16,473 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 00:23 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.