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 Sui package primarily manages a `DCA` (Dollar-Cost Averaging) object, which represents an automated trading strategy. Public/entry functions allow users to initialize a new `DCA` object, performing a swap of `Coin<Ty0>` for `Coin<Ty1>` (or vice-versa) through a `Pool` or a series of `Pool`s, and then resolving the trade. These functions mutate the `DCA` object by updating its `input_balance`, `last_time_ms`, and `remaining_orders`, and also transfer coins to the `DCA` owner. Notable patterns include time-gating (using `Clock` and `start_time_ms`, `last_time_ms`, `every` fields), dynamic fields (implicitly through generic types `Ty0`, `Ty1`), and a vault/escrow mechanism for `Coin<Ty0>` and `Coin<SUI>` within the `DCA` object. The `TradePromise` object is used to enforce price limits during swaps.
This package primarily manages a `FeeState` object, which tracks accumulated fees and user withdrawal amounts for two generic token types. Public functions allow users to `withdraw` their share of accumulated fees, calculated based on their stake. The package also includes an `admin` module for creating an `Admin` capability, an `errors` module for various error codes, and an `events` module for emitting `NewPool`, `Swap`, `AddLiquidity`, and `RemoveLiquidity` events. The `go_live` module, which requires an `Admin` capability, initializes a complex system involving `SeedPool`, `TreasuryCap`, and `VestingConfig` objects, and appears to set up a staking pool and distribute initial funds, including a fixed amount of SUI and a percentage of another token. The `FeeState` object uses dynamic fields (tables) to store `user_withdrawals_x` and `user_withdrawals_y`, and the `go_live` function is gated by an `Admin` capability.
This package manages a RefundPool object, which tracks funds for refunds and boosts. Public/entry functions allow a publisher to create new pools, add addresses and their refund amounts to a pool, and manage funding/withdrawal for both the base refund pool and a booster pool. Users can claim their refunds (potentially boosted) or reclaim their funds if the refund period ends. The RefundPool object mutates its internal Accounting and Pool structs, which track total raised, refunded, and boosted amounts, and manage individual funder balances. Notable patterns include publisher-gating for administrative actions, phase-gating (funding, claim, reclaim phases), and dynamic fields for BoostedClaimCap objects.
This package primarily manages a decentralized exchange (DEX) with staking and vesting functionalities. It introduces an `Admin` object for administrative control and `FeeState` to track and distribute fees. Public/entry functions allow users to create new liquidity pools, swap tokens, add/remove liquidity, and manage staking/vesting. Notable patterns include admin gating for critical operations, time-gating for vesting, and the use of dynamic fields within `FeeState` to manage user-specific withdrawal balances. The package also handles the distribution of fees to stakers and includes mechanisms for initial token distribution and vesting schedules.
This package defines a refund system centered around a RefundPool object. The RefundPool manages two internal Pool objects (base_pool and booster_pool) and an Accounting object to track various financial metrics like total raised, total to refund, and total claimed. Public/entry functions allow a designated publisher to add addresses and their corresponding refund amounts to the RefundPool, and users can fund both the base and booster pools with SUI. Claim functions enable users to claim their refunds, potentially boosted, during specific phases, which mutates the Accounting object and transfers SUI. The system uses dynamic fields for BoostedClaimCap management and enforces phase-gating and time-gating for certain operations.
Wallets that share a funder, were co-funded by the same personal-scale source, or land in the same behavioral cluster. A heuristic, not proof of common control.
Tinted amber on the bubble map when they appear in the expanded graph.
area + brightness = call volume; hover for detail
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": "0x935fd79d69b98dc87cd43d4112e621fe92967c7f33fa232ddf4f6351bb1b9a19",
"n_tx": 76,
"n_successful_tx": 58,
"n_distinct_epochs": 22,
"n_distinct_sponsors": 0,
"first_seen_cp": 27968517,
"last_seen_cp": 33027179,
"first_seen_ts_ms": 1709650015068,
"last_seen_ts_ms": 1714692613575,
"total_gas_spent_mist": 4671808428,
"n_self_sponsored_tx": 76,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
15,
17,
20,
14,
18,
21,
16,
10,
11,
12,
23,
19,
22,
13
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely Atlantic / E. South America.