MAXPAID
The curve completed in the same batch of events as the 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.
findingOnly 7 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteThe creator sold while we were watching.
noteOnly 1.6 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-18 10:30 UTC |
| Creator | C1dksGGCKHhpoESy5rJKrqyN6JvqKUbgg65Q6PN3tzFw |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 7 distinct wallets, not counting the creator, bought on the bonding curve: 7 within the first 30s, 7 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 | yes |
| Recorded from | 3GyLE3fqxW6MFmxPbBXDyp… slot 448,056,932
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-18 10:30:02 UTC Slot 448,056,932, which is the chain's own clock for this moment. |
| Creation block | 7 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-18 10:30:02 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 7 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. |
| Highest price seen | 2026-09-18 10:31:51 UTC +1m 49s
9.125e-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 | No other launch we hold a picture for used this one. |
Pool
| Liquidity | 1.6 SOL |
| Read from chain | 2026-09-18 22:07 UTC, just now |
What this launch claimed to be
| Name | Max Paid |
| Description | They thought they could buy the city. They thought everyone had a price. Max did too but his payment was different |
| Metadata held | sha256 8df5dae37517f1596d6e03e577e14fb8e75fe63dd5b123ea816333e6fe892b27 · 428 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 51f7e19989eec8857ba5773c0ae98e5aa274a8a25f53f6d0de4c5a468a171127 · 796,956 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-18 10:30 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.