Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-11-12 22:34 UTC |
| Creator | 54nFr9aDHRiuGeUtcUr8kZ8XzW4NTYpQEVkdZVraF7vd |
| Creator took | 1.9% of supply in the first block |
| Outside buyers | 176 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 71 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 1 min after launch |
| Curve on chain | Complete. We read the bonding curve account 4.8 h ago and it was finished. Checked 2026-11-12 23:00 UTC. |
| Creator sold | yes |
| Recorded from | 5xhrctD1ReMhVa8Jm5hDbX… slot 468,694,401
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Order of events
| Created | 2026-11-12 22:34:50 UTC Slot 468,694,401, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 71 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-11-12 22:35:54 UTC +1m 04s Confirmed against the venue's own completion state. |
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 | No other launch we hold a picture for used this one. |
| This ticker | On 86 launches from 64 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.6% wear one that more than one creator wallet has launched. See this ticker's page → |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | 1win |
| Metadata held | sha256 933093a26707726bc6ce5388f808928f95ed2a9b0027b38b4c0a8b6c00274fac · 221 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. |
| Picture held | sha256 53fe2d07b590c8af599634b8b1816b32408e930683bde72eb7ac54774c57d0b5 · 12,742 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 22:34 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.