LOOT
The curve completed 45s 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 45s after launch.
noteOnly 2.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-28 18:03 UTC |
| Creator | HzgAB5i5V7XWHUri43qg21fAj6icimpuaWJi6nLnqBwU |
| Creator took | 1.0% of supply in the first block |
| Outside buyers | 218 distinct wallets, not counting the creator, bought on the bonding curve: 180 within the first 30s, 14 bundled into the creation block. |
| Graduated | 1 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 | oUF4wuC4kX8iDRSPaw7MG3… slot 451,393,954
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-28 18:03:21 UTC Slot 451,393,954, which is the chain's own clock for this moment. |
| Creation block | 14 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 180 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-09-28 18:04:06 UTC +45s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-28 18:04:06 UTC +45s
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 170 launches from 123 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.7 SOL |
| Read from chain | 2026-09-28 21:10 UTC, just now |
What this launch claimed to be
| Name | LiquidLoot |
| Metadata held | sha256 1912fb108d233b5ba0d6c222c0d73ff07dd4a2347fbbffffa34c834eb1db3ee6 · 270 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 809223f5d819da28280c3efb6da05855e4a5de706ce78105bc86ee32cbedc498 · 9,747 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-28 18:03 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.