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` and `Nft` objects. The `init` function initializes a `Publisher` and a `Display<Nft>` object, transferring them to the transaction sender. Public entry functions allow the `Minter`'s owner to `add_phase`, `remove_phase`, and `update_phase` for sales, which involves modifying the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs, checking against sale phases, time-gating, and optionally using a Merkle tree for allowlist verification. Minting updates the `minted` count in the `Minter` and records user and phase-specific buys in `user_buys` and `sale_phase_buys` tables, and transfers the minted `Nft` to the sender.
This package defines a system for managing and minting NFTs within a collection. It primarily manages Minter objects, which represent an NFT collection's minting configuration, and Nft objects, which are the individual NFTs. The public/entry functions allow the Minter's owner to add, remove, and update SalePhase objects, which define different minting stages with specific prices, limits, and start times. The core mint function allows users to mint NFTs if they meet the criteria of the current active sale phase, verifying merkle proofs if required, and updating the Minter's minted count and user/phase buy counts. The mint function mutates the Minter object, transfers SUI coins, and creates new Nft objects. Notable patterns include: owner-gating for administrative functions (add_phase, remove_phase, update_phase), time-gating for sale phases, optional Merkle tree root verification for allowlists (root field in SalePhase), and the use of Sui's `table` module for tracking user and phase-specific mint counts.
This package defines a system for managing and minting NFTs. It 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, modifying the `phases` vector within the `Minter` object. The `mint` function allows users to purchase NFTs. This function checks against the current sale phase, user-specific mint limits, and total sales limits, and it also handles payments. The `mint` function mutates the `Minter` object by updating `minted`, `user_buys`, and `sale_phase_buys` fields, and it creates a new `Nft` object. Notable patterns include time-gating for sale phases, dynamic fields (`Table`) to track user and phase-specific purchases, and a Merkle tree verification (`verify`, `processProof`, `hashPair`) for potential allowlist functionality. The
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Nft` objects, the actual NFTs minted. The `init` function initializes the package by claiming a `Publisher` 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 the NFT collection. These functions modify the `phases` vector within a `Minter` object, which defines different sale stages with specific prices, sale limits, mints per user, start times, and optional Merkle roots for allowlisting. The `mint` function allows users to mint NFTs. It checks the current sale phase based on the `Clock` timestamp, verifies Merkle proofs if a root is present in the phase, and updates the `minted` count in the `Minter` object as well as user-specific and phase-specific buy counts stored in `Table`s within
This package defines a system for managing and minting NFTs. It primarily manages Minter objects, which represent an NFT collection's minting configuration, and Nft objects, which are the actual NFTs. Public/entry functions allow the Minter's owner to add, remove, and update sale phases within a Minter object. The mint function allows users to mint NFTs, which involves checking sale phase conditions (time, price, user mint limits, and an optional Merkle proof for allowlist gating), transferring SUI, creating a new Nft object, and updating the Minter's minted count and user/phase buy records. Notable patterns include: admin gating for phase management (only the Minter's owner can modify phases), time-gating for sale phases, optional allowlist gating using Merkle proofs (SalePhase.root), and dynamic fields (Table) to track user and sale phase specific mint counts.
True specific-lot profit from 255 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).
1 self-dealing round-trip excluded from the headline (gross incl. wash: $433).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
flippernft_traderRule-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": "0x37a34319bb57546d7cff4640df387c2b03900dd350f7da6cdce55114a920a935",
"n_tx": 4795,
"n_successful_tx": 4682,
"n_distinct_epochs": 111,
"n_distinct_sponsors": 1,
"first_seen_cp": 1572567,
"last_seen_cp": 238952323,
"first_seen_ts_ms": 1683121271286,
"last_seen_ts_ms": 1769533258336,
"total_gas_spent_mist": 11919021520,
"n_self_sponsored_tx": 4791,
"n_sponsored_tx": 4,
"gas_price_p50": 820,
"gas_price_p95": 950,
"active_hours_top24": [
18,
15,
9,
13,
17,
16,
19,
14,
8,
21,
10,
20,
12,
7,
11,
6,
22,
23,
0,
5,
1,
2,
4,
3
],
"primary_archetype": "flipper",
"labels": [
"flipper",
"nft_trader"
],
"label_confidence": [
0.95,
0.9
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely UK / W. Europe / W. Africa.
area + brightness = call volume; hover for detail