Also recorded, and not part of the finding above: this picture is on 3 other launches, all of them this same creator's, and this creator has 8 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, 12.8% of the launches whose picture we hold carry one only their own creator reused. 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-09-02 15:03 UTC |
| Creator | 5JMrXfUEmygscZBbqzUG3rreXni5ViPdynDBVDofXCWS |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 0 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: 3 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 11 min after launch |
| Curve on chain | Complete. We read the bonding curve account 62.8 days ago and it was finished. Checked 2026-09-09 23:04 UTC. |
| Creator sold | yes |
| Recorded from | Not recorded. This launch predates our keeping the creation transaction (2026-09-09), and its trade rows had been pruned by retention before the backfill could recover the signature from them. The figures above stand on our own observation alone, which is weaker than a citation, and we would rather say so than leave the gap unmarked. |
Order of events
| Created | 2026-09-02 15:03:32 UTC |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 3 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-02 15:15:01 UTC +11m 29s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-02 15:20:54 UTC +17m 21s
1.121e-7 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 4 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.8% of the launches whose picture we hold carry one only their own creator reused. See them → |
| This ticker | On 784 launches from 487 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 | 8 earlier launches. All 1 that reached the graduation threshold on our feed were read on chain, and none had completed. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches → |
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 | SILVER SPOON |
| Description | magic is about the money |
| Metadata held | sha256 6dde83ae86dba4d9e8f3ae0ea7ea8da0d97355e19cb4558f73fda606202d6592 · 320 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-09-23 01:02 UTC. |
| Picture held | sha256 b24ac7f52fbb15bea4c4aec0dda26af53c5db45da196c20cc3a7d210ee910a83 · 5,854 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 21:21 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.