What this launch shares with other launches
Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for five lists, or with Brand Protection at $79 a month for every list on every record. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.
Its own first blocks
Also recorded, and not part of the finding above: this picture is on 414 other launches from 3 creator wallets in all, and this creator has 661 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.5% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
| Its most recent other launches (UTC) | Ticker | Name | Mint |
|---|---|---|---|
| 14 Nov, 08:48 | APPLE | APPLE | ██████████ |
| 14 Nov, 08:01 | APPLE | APPLE | ██████████ |
| 14 Nov, 07:58 | APPLE | APPLE | ██████████ |
| 14 Nov, 07:57 | APPLE | APPLE | ██████████ |
| 14 Nov, 07:56 | APPLE | APPLE | ██████████ |
| 14 Nov, 07:56 | APPLE | APPLE | ██████████ |
| See all of this creator's launches → | |||
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-14 07:57 UTC |
| Creator | 7ThNaxDtgoGkYG2nfsxwBU6y98VmDcVAJC9SBbk4JmXb |
| Creator took | 71.8% of supply in the first block |
| Outside buyers | 1 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: 1 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 0 min after launch |
| Curve on chain | Complete. We read the bonding curve account 6.1 h ago and it was finished. Checked 2026-11-14 08:01 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4bcsR55vm25MWQHFpytVwt… slot 469,252,200
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-14 07:57:17 UTC Slot 469,252,200, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-11-14 07:57:20 UTC +3s Confirmed against the venue's own completion state. |
| Thirty seconds in | 1 distinct buyer, 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. |
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 363 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 1,528 launches from 882 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 → |
| This document | The same launch document, byte for byte, as 209 other launches, across 2 creator wallets in all. Across the archive, 33.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| This creator | 608 earlier launches. 56 reached the graduation threshold on our feed; we have read the curve account for 50, and 50 had not completed, 26 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 3 other creator wallets, across 5 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 so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.7% 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 61 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 | 8.8 SOL |
| Read from chain | 2026-11-14 14:05 UTC, just now |
What this launch claimed to be
| Name | APPLE |
| Description | RISE AND SHINE IPHONE 18 |
| Metadata held | sha256 0db88b9eda8949f0f15719afc2f3351724aa1babbd98406d1b9c0dcc561590be · 212 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 aa4de67b830c3992cd2513b8352e5334e765a7c874b5d1552b430223fe861752 · 186,553 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-14 07:57 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.