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. The `init` function initializes the package, creating a `Publisher` and a `Display<Nft>` object, then transfers them to the transaction sender. Public functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for sales, modifying the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs from a `Minter` object by paying a fee, checking against sale phases, and potentially using a Merkle tree for allowlist gating. Minting mutates the `Minter`'s `minted`, `user_buys`, and `sale_phase_buys` fields, and transfers the minted `Nft` object to the user.
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Collection` and `Nft` objects, though `Collection` seems to be a wrapper for `Minter` and `Nft` is the actual item minted. The public/entry functions allow the `Minter`'s owner to manage sale phases: `add_phase` adds a new `SalePhase` to the `Minter`'s `phases` vector, `remove_phase` removes a `SalePhase` by name, and `update_phase` modifies an existing `SalePhase`'s parameters. These functions mutate the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs from a `Minter` object. It checks for time-gating (start_time in `SalePhase`), verifies a Merkle proof if a root is provided in the `SalePhase`, and updates `user_buys` and `sale_phase_buys` tables
This package defines a system for managing and minting NFTs. The primary object types are `Minter`, which represents an NFT collection and its associated sale phases, and `Nft`, which is the actual NFT object. The `init` function initializes the package by claiming a `Publisher` object and creating a `Display<Nft>` object, both transferred 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 collection, including setting prices, maximum sales, mints per user, start times, and an optional Merkle root for allowlist gating. The `mint` entry function allows users to mint NFTs from a collection, checking against sale phase conditions like price, time, and Merkle proof if applicable. Notable patterns include owner-gating for administrative functions (`add_phase`, `remove_phase`, `update_phase`), time-gating for sale phases, and optional allowlist gating using Merkle proofs (`root` field in `Sale
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections, and `Nft` objects, which are the individual NFTs. Public/entry functions allow the `Minter`'s owner to `add_phase`, `remove_phase`, and `update_phase` for the NFT collection. These functions modify the `phases` vector within the `Minter` object, which defines different sale stages with varying prices, limits, and start times. The `mint` function allows users to purchase NFTs, checking against the active sale phase's rules, including price, supply limits, and an optional Merkle root for allowlist gating. Notable patterns include owner-gating for phase management, time-gating for sale phases, and the use of a Merkle tree (`root` in `SalePhase`) for allowlist verification during minting. The `Minter` object also tracks `minted` NFTs and `user_buys` and `sale_phase_buys` using dynamic tables. The `init
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` for the minting process, which are time-gated and can include a Merkle root for allowlist gating. The `mint` function allows users to mint NFTs, checking against the current active sale phase's price, maximum sales, mints per user, and Merkle proof if applicable. The `Minter` object tracks minted NFTs and user-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.
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": "0xa762aca1f3f594136aa972f6563bd25b7c19c0d6bbb1633c483a71990a939c6b",
"n_tx": 161,
"n_successful_tx": 158,
"n_distinct_epochs": 27,
"n_distinct_sponsors": 0,
"first_seen_cp": 1891505,
"last_seen_cp": 88241875,
"first_seen_ts_ms": 1683452578462,
"last_seen_ts_ms": 1733662102997,
"total_gas_spent_mist": 1657290564,
"n_self_sponsored_tx": 161,
"n_sponsored_tx": 0,
"gas_price_p50": 950,
"gas_price_p95": 990,
"active_hours_top24": [
17,
5,
16,
15,
13,
10,
14,
9,
19,
8,
7,
20,
11,
6,
21,
18,
12
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.5925
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely C. Europe / Africa / Middle East.