PUSH
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.
noteThe creator sold while we were watching.
noteOnly 3.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 13:36 UTC |
| Creator | F6wpXD6PxnV1MqtKkhW5xenmzkzLTM8J29wZUntDsvWu |
| Creator took | 10.0% of supply in the first block |
| Outside buyers | 430 distinct wallets, not counting the creator, bought on the bonding curve: 61 within the first 30s, 9 bundled into the creation block. |
| Graduated | 7 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 | yes |
| Recorded from | 5VjeMvoFci2u5UiJCGM5Mg… slot 452,302,953
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 13:36:20 UTC Slot 452,302,953, 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. |
| Thirty seconds in | 61 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-10-01 13:43:43 UTC +7m 22s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 13:43:43 UTC +7m 23s
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. |
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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 34 launches from 25 creator wallets, including this one. See them → |
Pool
| Liquidity | 3.7 SOL |
| Read from chain | 2026-10-01 22:04 UTC, just now |
What this launch claimed to be
| Name | Push |
| Description | Introducing PUSH. Get paid to push. Devs: launch a coin and use creator fees to put your community on payroll. Community: hold the coin, post about it and earn a share of those fees. You launch. They push. The fees pay. |
| Metadata held | sha256 d1b26a628d3d82802cdb25a35b296591cbb17068785f71d25412e654568cd892 · 503 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 ee231eb1e109a467204ebd99c6a4ed3a5025ddc9bc3d0537bc9dbcf1b18c7774 · 463,926 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 13:36 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.