WATCHCOIN
The curve completed 19s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
findingIt left the curve 19s after launch.
noteOnly 2.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 22:53 UTC |
| Creator | EpBuA6DSCQR8JVRg8qMixuwjo4Us2YnEcrTENQxPTMo3 |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 217 distinct wallets, not counting the creator, bought on the bonding curve: 217 within the first 30s, 9 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read 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 | 3j2iGFPSxbmgusmEkz6dsm… slot 451,781,710
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 22:53:50 UTC Slot 451,781,710, which is the chain's own clock for this moment. |
| Creation block | 9 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-29 22:54:09 UTC +19s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 22:54:09 UTC +19s
4.109e-7 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Thirty seconds in | 217 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. |
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 creator | 112 earlier launches, 8 confirmed graduated on chain, 1 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 40 other creator wallets, across 36 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 2.7 SOL |
| Read from chain | 2026-10-01 10:11 UTC, just now |
What this launch claimed to be
| Name | WatchCoin |
| Description | https://x.com/UseNosh/status/2105068385729987007?s=20 |
| Metadata held | sha256 fec41ce36c019aa9c59b22b6cd697ac7e236e18d36585a6e8b764f7800d3bcbd · 359 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-30 22:54 UTC. |
| Picture held | sha256 6d0cf521a0da4159a722298f6f2e3a26e57062a68734543ad98b04566624cff6 · 108,308 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 22:53 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.