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 dummy `AF_LP` struct. Its `init` function, which is likely an entry point, calls `amm_interface::create_lp_coin` to create a new LP coin using the `AF_LP` type and a constant value of 6, along with the transaction context. This suggests the package's primary purpose is to register or initialize a new LP token type within an AMM (Automated Market Maker) system. The `AF_LP` struct itself has no functional fields, indicating it serves as a marker or identifier for this specific LP coin.
This package defines a single object type, AWDA, which is a dummy struct. The `init` function is the only public/entry function. It creates a new fungible token (Coin) named "AWDA" with the symbol "AWDAWD" and a specified icon URL. It then freezes the CoinMetadata object and transfers the TreasuryCap for the new AWDA token to the transaction sender. The package does not exhibit any notable patterns like signature/allowlist gating, time-gating, dynamic fields, or vault/escrow functionality.
This Sui package defines a single module, `af_lp`, which primarily manages a dummy `AF_LP` object. The `init` function, which is likely called once during package deployment, creates a new LP coin of type `AF_LP` by calling `amm_interface::create_lp_coin`. This suggests the package integrates with an Automated Market Maker (AMM) interface, likely to register `AF_LP` as a liquidity provider token. The `AF_LP` struct itself contains only a `dummy_field: bool`, indicating it might be a placeholder or a marker type rather than holding significant data within the package. There are no other public or entry functions, nor any notable patterns like admin caps, vaults, or time-gating.
This package defines a dummy `AF_LP` object. Its `init` function, which runs once upon package deployment, calls `amm_interface::create_lp_coin` to register the `AF_LP` type as a liquidity pool coin with an initial supply of 5 units. This suggests the package is a placeholder or a minimal integration with an AMM (Automated Market Maker) interface, likely for testing or future expansion. The package doesn't define any public or entry functions for user interaction beyond this initial setup.
True specific-lot profit from 22 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_collectorRule-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": "0x6e98d84417f6577559debaccec691891dd027640a2305b6e716016ce34e4e9d6",
"n_tx": 1394,
"n_successful_tx": 1291,
"n_distinct_epochs": 94,
"n_distinct_sponsors": 1,
"first_seen_cp": 20845853,
"last_seen_cp": 202766650,
"first_seen_ts_ms": 1702547018947,
"last_seen_ts_ms": 1760899795750,
"total_gas_spent_mist": 3912173408,
"n_self_sponsored_tx": 1393,
"n_sponsored_tx": 1,
"gas_price_p50": 750,
"gas_price_p95": 751,
"active_hours_top24": [
15,
2,
14,
3,
7,
13,
8,
16,
6,
5,
12,
4,
9,
10,
11,
1,
0,
17,
22,
23,
20,
19,
21,
18
],
"primary_archetype": "nft_collector",
"labels": [
"nft_collector"
],
"label_confidence": [
0.67
],
"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