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, `STEAMM_LP_BALPHA_BSUI`, which represents a liquidity provider (LP) token for a bALPHA-bSUI pair. The `init` function, which is called once upon package deployment, creates the currency, sets its metadata (name, symbol, description, icon URL, and decimals), and then transfers the `TreasuryCap` to the deployer and shares the `CoinMetadata` object publicly. The `TreasuryCap` allows the deployer to mint or burn `STEAMM_LP_BALPHA_BSUI` tokens, while the `CoinMetadata` provides public information about the token.
This Sui package defines a single module, 'yohan', which manages a custom cryptocurrency named "YohanCoin" (symbol "JOhan"). The primary object type is the `YOHAN` coin. The `init` function is the only public/entry function; it creates the `YOHAN` currency, sets its metadata (name, symbol, description, icon URL), freezes the `CoinMetadata` object, and transfers the `TreasuryCap` for the `YOHAN` coin to the transaction sender. This establishes the initial supply control for the YohanCoin. The package utilizes standard Sui `coin` and `transfer` modules for currency creation and object management.
This package defines a single module `b_ns` that manages a custom fungible token named "bToken NS" with the symbol "bNS". The `init` function, which runs once during package deployment, creates this new currency. It initializes the `CoinMetadata` for the token, including its name, symbol, description, and icon URL, and then shares this metadata object publicly. It also creates a `TreasuryCap` for the `bNS` token and transfers it to the deployer of the package, allowing them to mint or burn `bNS` tokens. The package does not define any other public or entry functions, implying that further token management (minting/burning) would be done via the `TreasuryCap` object held by the deployer.
This Sui package, pokemon_x_sui, primarily manages Nft objects, which represent non-fungible tokens with attributes like name, description, media_url, and a VecMap of string attributes. The init function immediately aborts, indicating it's not intended for direct initialization. Public functions like mint_order, mint_nft, mint_edition_nft, and update_nft also immediately abort, suggesting their functionality is either unimplemented or handled via external calls. The create_nft_with_verification function creates a new Nft object and associates its ID with a Verification object from the 0launchpad module. The update_nft_with_verification function allows modification of an Nft's details (name, description, media_url, attributes) if the provided Verification object's NFT ID matches the target Nft and the caller possesses the KioskOwnerCap. This module utilizes the 0launchpad module for verification and the Kiosk module for managing NFTs, indicating a pattern of using external modules for core functionalities and potentially a form of admin gating via the
This Sui package defines a single module named `turing` which primarily manages a custom fungible token called `TURING`. The `init` function, which is called once upon package deployment, creates this new currency. It mints a `TreasuryCap<TURING>` and a `CoinMetadata<TURING>` object, then immediately transfers both to the deployer's address. The `TURING` struct itself is a dummy type, likely serving as a phantom type parameter for the `CoinMetadata` and `TreasuryCap` objects. The module does not expose any public or entry functions beyond the `init` function, meaning no further interaction with the `TURING` token (minting, burning, etc.) is directly possible through this module after deployment. The notable pattern is the creation and immediate transfer of a `TreasuryCap`, which grants the recipient the authority to manage the `TURING` token supply.
True specific-lot profit from 1 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).
nft_collectorflipperRule-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": "0x6676f8f1576988f735adeaf93772a86dc96c4ca4660ba301db4fd82b5afd0f12",
"n_tx": 4601,
"n_successful_tx": 4413,
"n_distinct_epochs": 486,
"n_distinct_sponsors": 4,
"first_seen_cp": 21215406,
"last_seen_cp": 283494922,
"first_seen_ts_ms": 1702913730204,
"last_seen_ts_ms": 1780677444669,
"total_gas_spent_mist": 23175084278,
"n_self_sponsored_tx": 4543,
"n_sponsored_tx": 58,
"gas_price_p50": 750,
"gas_price_p95": 757,
"active_hours_top24": [
16,
17,
15,
18,
14,
20,
21,
0,
22,
23,
19,
2,
1,
3,
10,
13,
4,
12,
11,
9,
5,
6,
8
],
"primary_archetype": "nft_collector",
"labels": [
"nft_collector",
"flipper"
],
"label_confidence": [
0.68,
0.5725
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely Atlantic / E. South America.
area + brightness = call volume; hover for detail