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, my_minter, primarily manages a Minter object, which acts as a central configuration for NFT collections. It also defines Collection and Nft objects, though Nft objects are created by the minter::mint function from another package. The public/entry functions allow the Minter's owner to add, remove, and update sale phases, which define pricing, maximum sales, mints per user, start times, and optional Merkle roots for allowlist gating. The mint function allows users to mint NFTs if they meet the criteria of the current sale phase, including price, supply limits, and Merkle proof verification. The mint function mutates the Minter object by updating minted counts and user/phase buy records, and it transfers SUI coins from the user to the Minter's owner.
This package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections, and `Nft` objects, which are the individual NFTs. The `init` function sets up display metadata for `Nft` objects and transfers a `Publisher` object and the `Display<Nft>` object to the transaction sender. Public functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for managing sale 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, checking against the current sale phase's conditions like price, supply limits, user-specific mint limits, and Merkle proof verification if an allowlist is active. Upon successful mint, an `Nft` object is created and transferred to the minter, and the `Minter` object's `minted` count and user/phase buy counts are updated.
This package defines a system for managing NFT collections and their minting processes. It primarily manages 'Collection' objects, which represent NFT collections, and 'Minter' objects, which control the minting parameters for a specific collection. The 'init' function initializes a 'Display<Nft>' object and transfers it along with a 'Publisher' object to the transaction sender. Public/entry functions allow the minter's owner to add, remove, and update sale phases within a 'Minter' object, which involves modifying the 'phases' vector. The 'mint' function allows users to mint NFTs from a 'Minter' object, checking against sale phase parameters like price, maximum sales, and mints per user, and potentially using a Merkle tree root for allowlist gating. Minting mutates the 'minted' count of the 'Minter' and the 'user_buys' and 'sale_phase_buys' tables, and creates a new 'Nft' object. Notable patterns include owner-gating for administrative functions, time-gating for sale
True specific-lot profit from 3 closed buy→sell round-trips of the same NFT (realized_roundtrip), wash-adjusted, valued at each leg's trade-hour USD. Excludes still-held inventory (that's unrealized).
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
{
"wallet": "0x26ec1c8caaf2d3d6e60a8518fde8a7a9897bac4f115a47cbfcd6fcdf23fa2abb",
"n_tx": 178,
"n_successful_tx": 177,
"n_distinct_epochs": 22,
"n_distinct_sponsors": 0,
"first_seen_cp": 2511044,
"last_seen_cp": 8931978,
"first_seen_ts_ms": 1684102104402,
"last_seen_ts_ms": 1690629472498,
"total_gas_spent_mist": 549095908,
"n_self_sponsored_tx": 178,
"n_sponsored_tx": 0,
"gas_price_p50": 915,
"gas_price_p95": 930,
"active_hours_top24": [
15,
17,
9,
14,
18,
10,
16,
8,
13,
11,
20,
12,
0,
23,
7,
21,
6,
19,
22
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.5875
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely C. Europe / Africa / Middle East.