ENEY
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 1.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 15:01 UTC |
| Creator | LUHt6VEZrSiRKuErUcCGj8ge4SKwwJ4bFRnjZyM1D4x |
| Creator took | 3.3% of supply in the first block |
| Outside buyers | 760 distinct wallets, not counting the creator, bought on the bonding curve: 119 within the first 30s, 21 bundled into the creation block. |
| Graduated | 5 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 7.4 h ago and it was finished. Checked 2026-10-02 15:31 UTC. |
| Creator sold | yes |
| Recorded from | tvcm3Ev54sg9jUgR4Ak5Cs… slot 452,644,730
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 15:01:55 UTC Slot 452,644,730, which is the chain's own clock for this moment. |
| Creation block | 21 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 119 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-02 15:06:59 UTC +5m 04s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-02 15:07:03 UTC +5m 08s
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 ticker | On 17 launches from 15 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 1.0 SOL |
| Read from chain | 2026-10-02 22:55 UTC, just now |
What this launch claimed to be
| Name | Eney |
| Metadata held | sha256 d1e5448ad6ea4a47e1a0b71fb310b09c4c856dc7bc4da293c70bf849be71d219 · 261 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 | Not captured, so we cannot show what it published. That is our storage budget, not a finding about the launch. |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 15:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.