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 a single module named `popo` that manages a custom coin type called `POPO`. The `init` function, which is automatically called during package deployment, creates this new `POPO` currency. It mints a large initial supply (10^19 units) of `POPO` coins and transfers them to the deployer of the package. Additionally, it shares the `CoinMetadata<POPO>` object publicly, making the coin's properties discoverable, and transfers the `TreasuryCap<POPO>` to a zero address, effectively burning it and preventing further minting of `POPO` coins. The package utilizes standard Sui coin functionalities and URL handling for metadata.
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Nft` objects for the individual NFTs and `CreatorCapability` for administrative control. The `init` function sets up display metadata for `Nft` objects and transfers a `CreatorCapability` to the deployer, granting them administrative privileges. Public/entry functions allow the `Minter` owner (determined by `CreatorCapability`) to manage sale phases: `add_phase` inserts new sale phases into a `Minter` object's `phases` vector, `remove_phase` deletes a phase by name, and `update_phase` modifies an existing phase's parameters. These functions mutate the `Minter` object. The `mint` function allows users to mint NFTs. It checks the current sale phase based on the `Clock` timestamp, verifies a Merkle proof against the phase's root (if set), and ensures the user hasn't exceeded per-user mint limits. It transfers SUI from the user'
This package manages a primary object type called `Minter`, which represents an NFT collection's minting configuration. It also defines `Collection` and `Nft` objects, but these are not directly managed by the `Minter` module's public functions. The `Minter` object contains details like the collection's name, description, owner, total supply, and a vector of `SalePhase` objects. Each `SalePhase` defines a specific minting period with its own price, maximum sales, mints per user, start time, and an optional Merkle root for allowlist gating. Public/entry functions allow the `Minter`'s owner to add, remove, and update `SalePhase` configurations. The `mint` function allows users to mint NFTs, which involves checking the current sale phase, verifying Merkle proofs if an allowlist is active, and handling payment. The `mint` function mutates the `Minter` object by updating the `minted` count and tracking user and phase-specific mint counts. Notable patterns include
This package defines a system for managing and minting NFTs. It primarily manages Minter objects, which represent an NFT collection, and Nft objects, which are the individual NFTs. The init function initializes the package by claiming a Publisher capability and creating a Display object for Nft, transferring both to the sender. It also creates and transfers a CreatorCapability to the sender, which likely grants administrative privileges. Public functions allow the Minter's owner to add, remove, and update SalePhase objects within a Minter. SalePhase objects define different sales stages with parameters like price, max sales, mints per user, start time, and an optional Merkle root for allowlist gating. The core mint function allows users to mint NFTs. It checks the current active sale phase based on the clock timestamp, verifies Merkle proofs if an allowlist is active for that phase, and enforces per-user and total mint limits. It then creates an Nft object, transfers it to the minter, updates the Minter's minted count and user/phase buy counts, and emits
This Sui package defines a minter for NFTs. It manages `Minter` objects, which represent an NFT collection's minting configuration, and `Nft` objects, which are the actual NFTs. Public functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` to control minting phases, which include price, max sales, mints per user, start time, and an optional Merkle root for allowlisting. The `mint` function allows users to mint NFTs if they meet the current phase's criteria, including payment and an optional Merkle proof. The `init` function creates a `Publisher` object, a `Display` object for `Nft` metadata, and a `CreatorCapability` object, transferring them to the transaction sender.
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.
flipperRule-based labels, conservative precision.
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": "0x0c8ef93246169a8da20d3824e902323b593de2967b32c5e7d34cabc9a35006b3",
"n_tx": 296,
"n_successful_tx": 280,
"n_distinct_epochs": 34,
"n_distinct_sponsors": 0,
"first_seen_cp": 16941485,
"last_seen_cp": 127844633,
"first_seen_ts_ms": 1698669700095,
"last_seen_ts_ms": 1743217714700,
"total_gas_spent_mist": 2702344924,
"n_self_sponsored_tx": 296,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
14,
9,
12,
0,
15,
13,
16,
7,
8,
2,
3,
1,
6,
17,
5,
11,
23,
22
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.6
],
"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. Circadian peak → likely C. Europe / Africa / Middle East.
area + brightness = call volume; hover for detail