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 package defines a "CreepyPopsCollection" object, which acts as a central registry for a collection of "CreepyPopsNft" objects. It also defines a "CreepyPopsCap" object, which serves as an admin capability for the collection. The public/entry functions allow users to mint "CreepyPopsNft" objects from the collection, add addresses to a whitelist, and for the admin to set the collection's release time and prices. Minting is gated by the collection's `max_supply` and `release` time, and whitelisted users pay a different price. The `mint` function mutates the `minted` count of the "CreepyPopsCollection" and removes the minter's address from the `whitelist` if they were whitelisted.
This package defines a CreepyPops NFT collection. The primary object types are CreepyPopsCollection (the collection itself), CreepyPopsNft (individual NFTs), and CreepyPopsCap (an admin capability). The `init` function creates and shares the CreepyPopsCollection object and transfers the CreepyPopsCap to the deployer. Public entry functions allow users to `mint` or `mint_with_multiple` NFTs from the collection, paying a price that varies based on a whitelist and release status. The `add_to_whitelist` and `add_to_whitelist_multiple` functions, gated by the CreepyPopsCap, allow adding addresses to a whitelist. The `set_release` and `set_price` functions, also gated by the CreepyPopsCap, allow modifying the collection's release time and price. Notable patterns include an admin cap for privileged operations, a whitelist for differential pricing, and time-gating for the release of the collection.
This package defines a single module, `token`, which manages a custom fungible token called `TOKEN`. The `init` function, which runs once on package deployment, creates the `TOKEN` currency by calling `coin::create_currency`. It then freezes the `CoinMetadata<TOKEN>` object, making its properties immutable, and transfers the `TreasuryCap<TOKEN>` object to the deployer of the package, allowing them to mint and burn `TOKEN`s. There are no other public or entry functions, meaning the token's supply and distribution are solely controlled by the initial deployer who receives the `TreasuryCap`. The package utilizes standard Sui framework modules for coin management and transfers.
This package defines a custom fungible token called `TOKEN`. The `init` function creates the `TOKEN` currency, mints an initial supply of 100 billion tokens to the deployer, and then freezes the `CoinMetadata` object while transferring the `TreasuryCap` to the deployer. The `transfer` entry function allows any user to transfer a `Coin<TOKEN>` object to another address. The package primarily manages `Coin<TOKEN>` objects and their associated `CoinMetadata` and `TreasuryCap`.
This package manages CreepyPopsCollection objects, which represent an NFT collection, and CreepyPopsNft objects, which are the individual NFTs. The CreepyPopsCap object acts as an admin capability. Public/entry functions allow users to mint NFTs (mint, mint_with_multiple), add addresses to a whitelist (add_to_whitelist, add_to_whitelist_multiple), and query whitelist status (is_whitelisted) or release status (is_released). The admin can set the collection's release time (set_release) and the general mint price (set_price). Notable patterns include an admin cap for privileged operations, a whitelist for discounted or early access minting, and time-gating for the collection's release. The mint function mutates the CreepyPopsCollection by incrementing the minted count and removing the minter from the whitelist if applicable, and transfers a newly created CreepyPopsNft to the minter.
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
botRule-based labels, conservative precision.
area + brightness = call volume; hover for detail
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": "0xafccb597485e309269dfa77dcf0dd5d798fced36f1194c5ca9b3d7ef4465f3dc",
"n_tx": 514,
"n_successful_tx": 511,
"n_distinct_epochs": 4,
"n_distinct_sponsors": 0,
"first_seen_cp": 1598288,
"last_seen_cp": 20920142,
"first_seen_ts_ms": 1683147770428,
"last_seen_ts_ms": 1702620862768,
"total_gas_spent_mist": 6528373104,
"n_self_sponsored_tx": 514,
"n_sponsored_tx": 0,
"gas_price_p50": 1000,
"gas_price_p95": 1000,
"active_hours_top24": [
2,
1,
0,
3,
21,
13,
23,
4,
6,
20,
15,
17,
16,
14,
12
],
"primary_archetype": "bot",
"labels": [
"bot"
],
"label_confidence": [
0.83040935
],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W. N. America (Pacific/Mountain).