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 manages `InscriptionSui20Collection` and `InscriptionSui20` objects. The `init` function initializes a `Publisher` object and a `Display` object for `InscriptionSui20`, transferring both to the transaction sender, then creates and shares an empty `InscriptionSui20Collection` object. The `deploy` entry function allows an authorized `InscriptionData` object to deploy a new inscription collection, setting its metadata fields like tick, max supply, mint amount, limit per mint, URI, description, and content, and marks the collection as deployed. The `mint` entry function allows users to mint `InscriptionSui20` objects from a deployed collection, provided they pay a fee in SUI and adhere to the collection's minting limits, transferring the newly minted inscription to the sender. The package utilizes dynamic fields for the `Display` object and interacts with an external `inscription` module for core inscription logic and fee management.
This package manages two primary object types: `InscriptionSui20Collection` and `InscriptionSui20`. The `init` function initializes the module, creating a `Publisher` object and a `Display` object for `InscriptionSui20`, transferring them to the deployer, and then creating and sharing an empty `InscriptionSui20Collection` object. The `deploy` entry function allows an authorized `InscriptionData` object to configure an `InscriptionSui20Collection` with details like tick, max supply, amount per mint, mint limit, URI, description, and content, setting its `is_deploy` flag to true. The `mint` entry function allows users to mint `InscriptionSui20` tokens by paying a fee in SUI, provided the mint amount is within the collection's limit and total supply, and transfers the newly minted `InscriptionSui20` to the caller. This package utilizes dynamic fields implicitly through the `inscription` module and manages an `InscriptionSui20Collection` as a shared object.
This package manages `InscriptionSui20Collection` objects, representing a collection of inscription-based tokens, and `InscriptionSui20` objects, which are the individual inscribed tokens. The `init` function initializes the module by creating and sharing an empty `InscriptionSui20Collection` object and a `Display` object for `InscriptionSui20` tokens. The `deploy` entry function allows an authorized address to configure an `InscriptionSui20Collection` with details like tick, max supply, amount per mint, mint limit, URI, description, and content, and then marks it as deployed. The `mint` entry function enables users to mint `InscriptionSui20` tokens from a deployed collection, provided they pay the required fee and adhere to the collection's minting limits; it transfers the newly minted `InscriptionSui20` object to the minter. The package uses dynamic fields implicitly through the `inscription` module for managing inscription data and relies on a `Fee` object for minting costs.
This package manages two primary object types: InscriptionSui20Collection, which stores metadata and state for an inscription collection, and InscriptionSui20, representing individual inscribed assets. 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 allows an authorized user to set the parameters (tick, max, amount, limit, URI, description, contents) for an InscriptionSui20Collection, marking it as deployed. The `mint` entry function enables users to mint InscriptionSui20 objects by paying a fee in SUI, with checks for minting limits and total supply, and then transfers the newly minted InscriptionSui20 to the caller. The package utilizes dynamic fields implicitly through the `inscription` module for managing inscription data and employs a shared object (InscriptionSui20Collection) to manage the collection's state.
This package manages `InscriptionSui20Collection` objects, which represent a collection of inscriptions, and `InscriptionSui20` objects, which are individual inscriptions. The `init` function initializes the module by creating a `Publisher` object and a `Display` object for `InscriptionSui20` (both transferred to the sender), and then creates and shares an empty `InscriptionSui20Collection` object. The `deploy` entry function allows the creator to configure an `InscriptionSui20Collection` with details like tick, max supply, mint amount, limit per mint, URI, description, and content, but only if it hasn't been deployed yet. The `mint` entry function allows users to mint `InscriptionSui20` objects from a deployed collection, provided they pay a fee and adhere to the collection's minting limits, and then transfers the newly minted inscription to the sender. The package uses dynamic fields implicitly through the `inscription` module for managing inscription data and fees.
True specific-lot profit from 17 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).
flippernft_collectornft_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": "0xac4a4cb5af95a3c251f3c0262777ec694504ca8d3bed8e6f9360c7fb85a4fb88",
"n_tx": 1959,
"n_successful_tx": 1929,
"n_distinct_epochs": 370,
"n_distinct_sponsors": 3,
"first_seen_cp": 2116287,
"last_seen_cp": 282687472,
"first_seen_ts_ms": 1683684745940,
"last_seen_ts_ms": 1780498000729,
"total_gas_spent_mist": 12510273124,
"n_self_sponsored_tx": 1941,
"n_sponsored_tx": 18,
"gas_price_p50": 750,
"gas_price_p95": 755,
"active_hours_top24": [
1,
2,
7,
12,
13,
6,
5,
14,
8,
3,
11,
4,
0,
10,
15,
9,
16,
23,
19,
17
],
"primary_archetype": "nft_collector",
"labels": [
"flipper",
"nft_collector",
"nft_trader"
],
"label_confidence": [
0.7,
0.95,
0.784
],
"bot_score": 0.3,
"bot_signals": [
"floor_arb_bot"
],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.
area + brightness = call volume; hover for detail