all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
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 a new fungible token called "SAT" (Satoshi). The primary object types it manages are CoinMetadata<SAT> and TreasuryCap<SAT>. The init function, which is an entry function, creates the SAT currency with a symbol "SAT", name "Satoshi", and an empty description. It then mints 1,000,000,000 SAT tokens to the sender of the transaction and shares the CoinMetadata<SAT> object publicly. The TreasuryCap<SAT> object is transferred to a hardcoded zero address, effectively burning it or making it inaccessible for further minting by the creator. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, or vault/escrow mechanisms.
This Sui package defines a single module, `fdfd`, which primarily manages a custom fungible token represented by the `FDFD` struct. The `init` function, which is an entry point, creates this new currency with a fixed supply of 3,333,000,000,000 units. It then mints this entire supply and transfers it to the transaction sender. Finally, it shares the `CoinMetadata<FDFD>` object publicly and transfers the `TreasuryCap<FDFD>` to a hardcoded zero address, effectively burning or locking the minting authority. There are no other public or entry functions, nor any notable patterns like signature gating, time-gating, or dynamic fields.
The `kumo` package introduces a primary object type `KUMO`, which appears to be a representation of a fungible token. The `init` function is the only public entry point, responsible for creating and configuring this `KUMO` token. It initializes the token's metadata (name, symbol, description, icon URL) and sets up its treasury. During initialization, the `init` function conditionally mints an initial supply of `KUMO` tokens to the transaction sender if a specific configuration value is greater than zero. It also sets a maximum supply for the token, again based on a configuration value. Finally, it conditionally creates and transfers `MintCap`, `BurnCap`, and `MetadataCap` objects to the transaction sender, and can optionally allow public burning of the token. The `IPXTreasuryStandard` and `CoinMetadata<KUMO>` objects are then shared publicly. Notable patterns include the use of `TreasuryCap` and `CoinMetadata` for managing the fungible token, and the `IPXTreasuryStandard` and `Witness
This package defines a `GEEK` coin, which is the primary object type it manages. The `init` function creates the `GEEK` coin, its metadata (name "Geek", symbol "Uber", description "Ubergeek"), and an `IPXTreasuryStandard` object. It also conditionally mints an initial supply of `GEEK` coins to the sender, sets a maximum supply, and creates and transfers `MintCap`, `BurnCap`, and `MetadataCap` objects to the sender based on configuration. Finally, it can optionally allow public burning of the coin and shares the `IPXTreasuryStandard` and `CoinMetadata` objects. This package utilizes the `ipx_coin_standard` for managing the coin's treasury and capabilities.
This package defines a single object type, `MEDICI`, which is a dummy struct used as a type parameter for a fungible token. The `init` function is the only public/entry function and it creates a new fungible token with the symbol "MEDICI" and name "satoshi". It initializes the token's metadata, creates a `TreasuryCap` for minting, and an `IPXTreasuryStandard` object to manage the token. The `init` function also conditionally mints an initial supply to the sender, sets a maximum supply, and creates and transfers `MintCap`, `BurnCap`, and `MetadataCap` objects to the sender based on boolean flags. Finally, it conditionally allows public burning and shares the `IPXTreasuryStandard` and `CoinMetadata` objects. This package primarily uses the IPX Coin Standard for token management and includes conditional gating for various token functionalities.
True specific-lot profit from 25 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).
flipperRule-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": "0x40061c709edb896ad029c500de2aee3ef58a062a4b3bd05235d5ae3df6586d8b",
"n_tx": 4943,
"n_successful_tx": 4808,
"n_distinct_epochs": 458,
"n_distinct_sponsors": 3,
"first_seen_cp": 5016546,
"last_seen_cp": 282351729,
"first_seen_ts_ms": 1686659317976,
"last_seen_ts_ms": 1780423167063,
"total_gas_spent_mist": 57537816130,
"n_self_sponsored_tx": 4922,
"n_sponsored_tx": 21,
"gas_price_p50": 750,
"gas_price_p95": 758,
"active_hours_top24": [
2,
3,
16,
19,
17,
20,
9,
10,
21,
18,
15,
1,
22,
14,
23,
4,
0,
11,
8,
13,
12,
7,
5,
6
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.655
],
"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