INUVEST
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
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 2.8 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 22:22 UTC |
| Creator | AU6TE3h6N3XD7L8KZW5FbFeN32GkAhfDhYrHKGDJVUoh |
| Creator took | 1.0% of supply in the first block |
| Outside buyers | 251 distinct wallets, not counting the creator, bought on the bonding curve: 60 within the first 30s, 3 bundled into the creation block. |
| Graduated | 5 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 6.4 h ago and it was finished. Checked 2026-10-01 22:31 UTC. |
| Creator sold | not while we watched |
| Recorded from | 2j4S47zKnVL4d3sK95EXEE… slot 452,420,410
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 22:22:24 UTC Slot 452,420,410, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 60 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 22:27:24 UTC +4m 59s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-01 22:27:24 UTC +4m 59s
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 | No other launch we hold a picture for used this one. |
| This ticker | On 23 launches from 17 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.8 SOL |
| Read from chain | 2026-10-02 04:56 UTC, just now |
What this launch claimed to be
| Name | INUVESTMENTS |
| Metadata held | sha256 dae457abf1aba31f74e5260cf9a3c2bec26bd2e66dc463bce9eeb1c8849fe7d3 · 271 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 58b418e7b76a0fc6c0c58e92b9dd325b353758a0597164c54384a8018747fe55 · 5,570 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 22:22 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.