all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
counterparties · funders · clusters
Move packages this wallet published on-chain — what it shipped, not what it used.
This Sui package defines two primary object types: `Launchpad` and `Pad`. The `Launchpad` object tracks the overall progress of a token sale, including the owner, token price, total tokens available, and tokens sold. The `Pad` object, which is generic over two coin types (inventory and proceeds), represents an individual sale pad with an owner, price per unit, tokens sold, and balances for inventory and collected proceeds. Public functions for `Launchpad` allow initialization, purchasing tokens (which increments `tokens_sold` if within limits), and querying the number of tokens sold or remaining. Entry functions for `Pad` enable its initialization (sharing the object), depositing inventory tokens, and withdrawing unsold tokens or collected proceeds, all of which are restricted to the `Pad`'s owner. The `buy` entry function facilitates purchasing tokens from a `Pad` by transferring payment and receiving inventory tokens, updating the `Pad`'s `sold` count and `proceeds` balance. Notable patterns include owner-gating for `Pad` operations (deposit,
This Sui package defines a `USD` coin type. The `init` function, which runs once on package deployment, creates the `USD` currency with 9 decimal places, a name "USD", a symbol "USD", and a description "USD Stable Coin", along with a base64 encoded image URL. It then mints a large initial supply (77,777,777.000000000 USD) and transfers it to the deployer of the contract. Finally, it transfers the `TreasuryCap<USD>` to address `0x0` (effectively burning it or making it inaccessible for further minting by the deployer) and shares the `CoinMetadata<USD>` object publicly. The package primarily manages `CoinMetadata<USD>` and `TreasuryCap<USD
This Sui package, `sum_sui`, primarily manages a custom cryptocurrency object type called `SUM_SUI`. The `init` function is the only public/entry function, and it creates a new currency, mints an initial supply, and transfers the `TreasuryCap` (which controls minting/burning) to the transaction sender while publicly sharing the `CoinMetadata` object. The module does not exhibit patterns like signature/allowlist gating, time-gating, dynamic fields, vault/escrow, or royalties.
This package defines a single module, `king`, which primarily manages a custom coin type called `KING`. The `init` function, which is called once during package deployment, creates this `KING` currency, setting its name, symbol, description, and icon URL. It then freezes the `CoinMetadata<KING>` object, making it immutable, and transfers the `TreasuryCap<KING>` to the sender of the transaction. This pattern indicates the creation of a new fungible token with an initial administrator (the sender) who holds the treasury cap, allowing them to mint or burn `KING` tokens.
This package defines an `Nft` object type, representing a non-fungible token with fields for `id`, `name`, `description`, `media_url`, and `attributes` (a `VecMap` of strings). The `init` function and several public/entry functions (`mint_order`, `mint_nft`, `mint_edition_nft`, `update_nft`) immediately abort, suggesting they are either placeholders or their implementations were removed/commented out. The `create_nft_with_verification` function creates a new `Nft` object, initializes its fields from provided arguments, and then calls an external `launchpad::set_verification_nft_id` function, passing the newly created NFT's ID. The `update_nft_with_verification` function allows modification of an existing `Nft`'s `name`, `description`, `media_url`, and `attributes`, but only if the provided `Nft`'s ID matches a verified ID from an external `launchpad` module. Both `create_nft_with_
True specific-lot profit from 9 closed buy→sell round-trips of the same NFT (realized_roundtrip), wash-adjusted, valued at each leg's trade-hour USD. Excludes still-held inventory (that's unrealized).
1 self-dealing round-trip excluded from the headline (gross incl. wash: -$191).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
Wallets that share a funder, were co-funded by the same personal-scale source, or land in the same behavioral cluster. A heuristic, not proof of common control.
Where this wallet's SUI first came from, and what it seeded downstream. Observational: a CEX funder suggests a real/retail origin; a high-fanout non-CEX funder is a signal worth noting — not proof of anything.
{
"wallet": "0x61ada65a59efa98b7c83aaf8c60beb38a517ccae7b0937838797dd65056c8a67",
"n_tx": 1010,
"n_successful_tx": 988,
"n_distinct_epochs": 108,
"n_distinct_sponsors": 2,
"first_seen_cp": 70211817,
"last_seen_cp": 271579887,
"first_seen_ts_ms": 1729243055633,
"last_seen_ts_ms": 1777791499109,
"total_gas_spent_mist": 5938976216,
"n_self_sponsored_tx": 999,
"n_sponsored_tx": 11,
"gas_price_p50": 740,
"gas_price_p95": 740,
"active_hours_top24": [
18,
7,
14,
21,
15,
12,
6,
22,
10,
16,
3,
19,
17,
8,
11,
23,
13,
2,
9,
5,
1,
20,
0,
4
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Tinted amber on the bubble map when they appear in the expanded graph.
Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail