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, `my_minter`, primarily manages `Minter` objects, which represent NFT collections, and `Nft` objects, which are the individual NFTs. The `init` function creates a `Publisher` and a `Display<Nft>` object, transferring both to the transaction sender. Public/entry functions include `add_phase`, `remove_phase`, and `update_phase`, all of which modify the `phases` vector within a `Minter` object, but only if the transaction sender is the `Minter`'s owner. The `mint` function allows users to mint NFTs from a `Minter` object, checking against sale phases, user-specific mint limits, and total supply limits. It also verifies a Merkle proof if a root hash is provided for the current sale phase. The `mint` function mutates the `Minter` object's `minted` count, `user_buys` table, and `sale_phase_buys` table, and creates a new `Nft` object. Notable patterns include
This package defines a minter for NFTs, centered around the Minter object. It allows for the creation of NFT collections with multiple sale phases, each having a price, optional maximum sales, optional mints per user, a start time, a name, and an optional Merkle root for allowlist gating. The public functions enable the Minter's owner to add, remove, and update these sale phases, ensuring that only the owner can modify the minting schedule and parameters. The core mint function handles the actual NFT creation, verifying the current time against sale phase start times, checking user and phase-specific mint limits, and optionally validating a Merkle proof against a provided root. Minted NFTs are transferred to the caller, and the collected SUI coins are transferred to the Minter's owner.
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.
area + brightness = call volume; hover for detail
{
"wallet": "0x93e6f61dec27596cc725c67b8fb8d577d2d30a76b0cb49c615ec4286b0e5ec49",
"n_tx": 32,
"n_successful_tx": 32,
"n_distinct_epochs": 5,
"n_distinct_sponsors": 0,
"first_seen_cp": 1805004,
"last_seen_cp": 113866946,
"first_seen_ts_ms": 1683361036318,
"last_seen_ts_ms": 1739859016031,
"total_gas_spent_mist": 250170296,
"n_self_sponsored_tx": 32,
"n_sponsored_tx": 0,
"gas_price_p50": 990,
"gas_price_p95": 1000,
"active_hours_top24": [
11,
18,
12,
8,
13,
16,
6
],
"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. Circadian peak → likely W/Central Asia / India.