zMilk
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-19 22:29 UTC |
| Creator | 4K7dnDDQTcptPZVQPcYc47bX66Ch96iQZbPeY1DKRpjD |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 25 distinct wallets, not counting the creator, bought on the bonding curve: 1 within the first 30s, 0 bundled into the creation block. |
| Graduated | 6 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 | 5phPEbY7FaA8QR7uJeizhX… slot 448,542,734
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-19 22:29:48 UTC Slot 448,542,734, 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 | 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. |
| Curve completed | 2026-09-19 22:35:33 UTC +5m 45s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-19 22:38:00 UTC +8m 12s
1.107e-6 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. |
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. |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-09-20 08:54 UTC, just now |
What this launch claimed to be
| Name | zMommy |
| Description | buy to bounce |
| Metadata held | sha256 7abc832e7eaadeadf7e1dd8ef132708bb2dcbdd330a211c14b0ea09b157f21ae · 306 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 37491baaeb8da7203ea24e51c045ee4322ec3b4141576e0f94903fe269d8e5b0 · 176,650 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-19 22:29 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.