Also recorded, and not part of the finding above: this picture is on 15 other launches from 3 creator wallets in all, and this creator has 10 other launches on record. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
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 08:06 UTC |
| Creator | 279wv4A6kjW9SZdhdkmVPCiiw23By9P6WBqJ5oJ5SB3d |
| Creator took | 67.2% of supply in the first block |
| Outside buyers | 33 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: 7 within the first 30s, 1 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | 2 min after launch |
| Curve on chain | Complete. We read the bonding curve account 7.2 h ago and it was finished. Checked 2026-11-12 08:30 UTC. |
| Creator sold | not while we watched |
| Recorded from | 5yMwtwyGXBH79WeDx7ZwBQ… slot 468,452,025
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 08:06:06 UTC Slot 468,452,025, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 7 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 08:08:10 UTC +2m 03s 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 | On 16 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 16 launches from 3 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.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 10 earlier launches, 1 confirmed complete on chain, 3 with findings on record. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 2 other creator wallets, across 2 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group of 3 creator wallets in all. Across the archive, 63.9% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Who took the curve
One transaction bought 50 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →
That is the same transaction the token was created in: the launch and the purchase of its float are one signature.
Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.
Pool
| Liquidity | 1.0 SOL |
| Read from chain | 2026-11-12 15:43 UTC, just now |
What this launch claimed to be
| Name | ZEPHYRON |
| Description | The pool locks at launch, the fee can only go down, and every buyer reads the rules before the first trade. |
| Metadata held | sha256 a4d26fd34f8aa38b6bcedbb60fee9c539030990c47c85e981826cbc7689dff43 · 439 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 4cb8328f9776b12f2a3ce5dad2ff3b5d0a7cc2ea4ef049731f9e0b37147a040d · 329,978 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 08:06 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.