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 1 other launch, and this creator has 9 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. They are listed under Seen before, further down this page.
At launch
| Created | 2026-11-14 12:06 UTC |
| Creator | GaUHMhuPKyT2RyD3gJnTvtoTLxN3VhvheuwNZ9fzGacP |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 18 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: 2 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 1 min after launch |
| Curve on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not while we watched |
| Recorded from | 45EjZ5oWSwSHGQazVvCaEp… slot 469,321,582
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 12:06:01 UTC Slot 469,321,582, 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 | 2 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-14 12:07:05 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 creator | 6 earlier launches, none of which reached a graduation threshold while we watched. 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 | STRATCOM |
| Description | Get in now, HODL with vision, and let your portfolio do the talking! |
| Metadata held | sha256 0c153ca6cf44ba2907d9e67949d5ca34f85be24c4a2611754355756afe5ced8d · 260 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 7c22dcaa217627012ba08118329408d4606f60151dbe14bb214226f74d138c1a · 102,942 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-14 12:06 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.