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 an "InscriptionSui20Collection" object, which represents a collection of "InscriptionSui20" objects. The `init` function initializes the module by creating a shared `InscriptionSui20Collection` object and a `Display` object for `InscriptionSui20`, transferring both to the sender. The `deploy` entry function allows for setting up the `InscriptionSui20Collection`'s metadata (tick, max, amount, limit, URI, description, and contents) and marks it as deployed, but only if it hasn't been deployed before. The `mint` entry function allows users to mint `InscriptionSui20` objects from a deployed collection, checking against the collection's `lim` and `max` values, and transfers the minted object to the caller. It also interacts with an external `inscription` module for deployment and inscription logic, and a `Fee` object for fee handling.
This Sui package defines a custom coin type called `WZ`. The `init` function, which runs once upon package deployment, creates this new `WZ` currency. It initializes the coin's metadata (symbol "WZ", name "wangzai", description "wangzai milk", and an icon URL) and a `TreasuryCap<WZ>`. The `CoinMetadata<WZ>` object is then frozen, making it immutable, while the `TreasuryCap<WZ>` is transferred to the deployer of the package. This `TreasuryCap` object is crucial as it grants the holder the ability to mint or burn `WZ` tokens. The package primarily manages the `CoinMetadata<WZ>` and `TreasuryCap<WZ>` objects, with the latter being a form of admin capability.
This package manages two primary object types: InscriptionSui20Collection, which stores metadata for an inscription collection, and InscriptionSui20, representing individual inscriptions. The 'init' function initializes the module, creating and sharing an empty InscriptionSui20Collection object and transferring a Publisher and Display object to the sender. The 'deploy' entry function populates the InscriptionSui20Collection with details like tick, max supply, mint amount, limit per mint, URI, description, and content, marking the collection as deployed. The 'mint' entry function allows users to mint InscriptionSui20 objects, checking against the collection's minting limits and charging a fee in SUI, then transferring the newly minted inscription to the sender. A notable pattern is the use of an external 'inscription' module for core inscription logic and a 'is_deploy' flag to gate the 'deploy' function, ensuring it can only be called once.
This package defines two primary object types: `InscriptionSui20Collection` and `InscriptionSui20`. The `init` function initializes a `Display` object for `InscriptionSui20` and creates an `InscriptionSui20Collection` object, which is then shared. The `deploy` entry function allows for the deployment of a new SUI20 inscription by setting parameters like tick, max supply, amount per mint, and mint limit within an `InscriptionSui20Collection` object, but only if it hasn't been deployed before. The `mint` entry function enables users to mint `InscriptionSui20` tokens, transferring a fee to a `Fee` object and updating the `current_mint` count in the `InscriptionSui20Collection`. Notable patterns include the use of a `Display` object for metadata, and a check in `deploy` to ensure it's a one-time operation.
This package defines two primary object types: InscriptionSui20Collection, which stores metadata about an SUI20 inscription collection (tick, max supply, mint amount, limit per mint, URI, description, content, and current mint count), and InscriptionSui20, representing an individual inscribed token with its name, URL, ID, description, and content. The `init` function initializes a new InscriptionSui20Collection object and shares it, along with a Publisher and Display object, with the transaction sender. The `deploy` entry function allows an address to configure an InscriptionSui20Collection by setting its properties, but only if the collection has not been deployed yet. The `mint` entry function enables users to mint InscriptionSui20 tokens from a deployed collection, provided they pay a fee and adhere to the collection's minting limits, transferring the newly minted InscriptionSui20 to the sender. The package utilizes dynamic fields for Display objects and integrates with an external `inscription` module for core inscription logic and fee
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
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": "0xcd2d72e01a1a83022da468cdef624c2cf258fa484f583de73ec723ce93487967",
"n_tx": 1348,
"n_successful_tx": 1314,
"n_distinct_epochs": 237,
"n_distinct_sponsors": 3,
"first_seen_cp": 6416812,
"last_seen_cp": 280351935,
"first_seen_ts_ms": 1688090411414,
"last_seen_ts_ms": 1779899427931,
"total_gas_spent_mist": 6155387588,
"n_self_sponsored_tx": 1304,
"n_sponsored_tx": 44,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
16,
13,
15,
14,
2,
3,
4,
12,
7,
9,
5,
8,
6,
1,
10,
17,
11,
18,
23,
0,
19
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail