landscape
Nobody bought its curveRead 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 completed its bonding curve with zero outside buyers on record.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 07:12 UTC |
| Creator | BU477U77PC1EgjFihmEkCf4gyk6v4arR2J1b6q8onJvR |
| Creator took | 2.5% of supply in the first block |
| Outside buyers | 0 distinct wallets, not counting the creator, bought on the bonding curve: 0 within the first 30s, 4 bundled into the creation block. |
| Graduated | 6.3 h 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 | 4kJfyBWQJzUgKZsUdGffy8… slot 451,893,587
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 07:12:08 UTC Slot 451,893,587, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-09-30 07:12:08 UTC
0.000e+0 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 | No 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-30 13:28:44 UTC +6h 16m 36s Confirmed: a PumpSwap pool was found for it. |
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-30 21:01 UTC, just now |
What this launch claimed to be
| Name | catonfone |
| Description | post trading the cat rotates fone to landscape for some nutflex |
| Metadata held | sha256 15d53dc4de92b38b28c4c37310ed63477a8ba56dc500f633a11b027b3f035bb3 · 331 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 659a7954f2c8073eb1043fa0674455f16a76d236b096798930eb178eab4e4b32 · 144,536 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 07:12 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.