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 system for managing and minting NFTs. The primary object types are `Minter` (representing an NFT collection's minting configuration), `Collection` (representing the NFT collection itself), and `Nft` (representing an individual NFT). The `Minter` object holds details like the collection ID, owner, total minted count, supply, name, description, and a vector of `SalePhase` objects. Each `SalePhase` defines a specific sale period with a price, maximum sales, mints per user, start time, name, and an optional Merkle root for allowlist gating. The `Minter` also uses tables to track user buys and sales per phase. Public/entry functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` to manage the sale phases. The `mint` function allows users to mint NFTs, which involves checking sale phase conditions (time-gating, allowlist gating using Merkle proofs, and per-user/per-phase mint limits),
This package defines a system for managing NFT collections and their minting processes. It primarily manages Minter objects, which represent an NFT collection's minting configuration, and Nft objects, which are the actual NFTs. Public functions allow the Minter's owner to add, remove, and update SalePhase objects within a Minter. SalePhase objects define different stages of the minting process, including price, maximum sales, mints per user, start time, and an optional Merkle root for allowlist gating. The mint function allows users to mint NFTs if they meet the criteria of the current active sale phase, which includes time-gating, price checks, and optional allowlist verification using Merkle proofs. The package utilizes dynamic fields through the Table type for tracking user-specific and sale phase-specific mint counts. It also includes a custom Merkle proof verification logic (compare_vector, hashPair, extract_vector, processProof, verify) for allowlist gating. The init function initializes a Display object for Nft metadata and transfers it to the deployer.
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. The `init` function initializes the package by claiming a `Publisher` object and creating a `Display<Nft>` object, transferring both to the transaction sender. Public/entry functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for sales, modifying the `phases` vector within a `Minter` object. The `mint` function allows users to mint NFTs from a `Minter` object, checking sale phase conditions, verifying Merkle proofs if a root is set, and updating `minted` count, `user_buys`, and `sale_phase_buys` tables. The `mint` function also creates an `Nft` object and transfers it to the minter, while transferring the payment `Coin<SUI>` to the `Minter` owner.
This Sui package defines a Minter object that manages the creation and distribution of Nft objects within a Collection. The Minter object contains sale phases (SalePhase) with configurable prices, maximum sales, mints per user, start times, and optional Merkle roots for allowlisting. Public functions allow the Minter's owner to add, remove, and update these sale phases, and a `mint` function enables users to purchase NFTs. The `mint` function performs time-gating based on the current sale phase's start time, manages per-user and per-phase mint counts using dynamic fields (Tables), and includes Merkle proof verification for allowlisted sales. NFTs are minted with unique IDs, names, descriptions, image URLs, and creator addresses, and the SUI payment is transferred to the Minter's owner.
This Sui package, `my_minter`, primarily manages `Minter` and `Nft` objects. The `init` function initializes the package by creating and transferring a `Publisher` and a `Display<Nft>` object to the transaction sender. The `add_phase`, `remove_phase`, and `update_phase` entry functions allow the `Minter`'s owner to manage sale phases within a `Minter` object, modifying its `phases` vector. The `mint` function allows users to mint `Nft` objects, checking against sale phase conditions (time, price, user limits, and an optional Merkle root for allowlisting). The `mint` function also updates the `minted` count in the `Minter` and records user and phase-specific purchase counts using dynamic fields (Tables).
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.
Tinted amber on the bubble map when they appear in the expanded graph.
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": "0x5615699dfceca2cf50307881e382d5bda6a827681c8d3798d7fd80cb5de0e4cd",
"n_tx": 296,
"n_successful_tx": 295,
"n_distinct_epochs": 10,
"n_distinct_sponsors": 0,
"first_seen_cp": 1829634,
"last_seen_cp": 2804118,
"first_seen_ts_ms": 1683387223804,
"last_seen_ts_ms": 1684412718340,
"total_gas_spent_mist": 5203962688,
"n_self_sponsored_tx": 296,
"n_sponsored_tx": 0,
"gas_price_p50": 990,
"gas_price_p95": 995,
"active_hours_top24": [
16,
17,
15,
8,
22,
9,
11,
10,
12,
18,
6,
19,
21,
20,
23,
5,
13,
4,
7,
2,
14
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.7525
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely C. Europe / Africa / Middle East.
area + brightness = call volume; hover for detail