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, `fetcher`, primarily interacts with `clob_v2::Pool` objects to retrieve order book data. It defines `PriceData` and `PriceRange` structs for internal use, and `FetchDeepbookStatusEvent` to emit results. The public entry functions, `fetch_deepbook_status_bid_side` and `fetch_deepbook_status_ask_side`, query the DeepBook CLOB for bid and ask side order book statuses, respectively. These functions take a `Pool` object, a `depth_level` (1-10), a `price_interval`, and optional `next_tick_level` and `next_order_id` for pagination. They calculate price ranges based on the `price_interval`, fetch order data from `clob_v2`, sum the depth within each range, and emit a `FetchDeepbookStatusEvent` containing the processed price data and pagination information. The package does not mutate the `Pool` object, but rather reads from it. There are no notable patterns like
This package defines functions to fetch and emit Deepbook order book status. It manages `PriceData` structs, which contain a price and depth. The `test` entry function emits a `TestEvent` with two arbitrary `u64` values. The `fetch_deepbook_status_bid_side` and `fetch_deepbook_status_ask_side` entry functions query the Deepbook CLOB for bid and ask side order book data, respectively, within a specified price range and depth. They then calculate aggregated price and depth information and emit a `FetchDeepbookStatusEvent2` containing the market price, high/low prices, vector lengths, and a vector of `PriceData`. Both fetching functions include checks to ensure the input `Arg1` (likely a count) is between 1 and 10, and `Arg2` (likely a price step) is greater than 0, aborting if these conditions are not met.
This Sui package manages lists of "CoinInfo" objects, which contain details like name, symbol, address, and extensions for various coins. The primary object types are "Registry" (a shared object storing all registered CoinInfo keyed by "CoinKey") and "List" (a transferable object holding a subset of CoinKeys). Public/entry functions allow for creating these lists, adding/removing approvers to/from them, and adding/removing CoinInfo entries to/from the registry or a specific list. Notably, adding/removing CoinInfo can be done by a signer (requiring a TreasuryCap) or by an approver (requiring approver status). The package utilizes dynamic fields for extensions within CoinInfo and employs an AdminCap for managing approvers.
This Sui package, `fetcher`, primarily manages `PriceData` structs, which contain a price and depth. It defines two entry functions: `fetch_deepbook_status_bid_side` and `fetch_deepbook_status_ask_side`. Both functions interact with a `clob_v2::Pool` object to retrieve market price and level 2 book status for either the bid or ask side, respectively. They then aggregate this information into a vector of `PriceData` and emit a `FetchDeepbookStatusEvent2` event, which includes the fetched prices, calculated price ranges, and vector lengths. A notable pattern is the use of `clob_v2::Pool` as a generic type parameter, indicating interaction with a decentralized exchange or order book.
This package defines two primary object types: `PriceData` (price and depth) and `PriceRange` (low and high price). It also defines an event `FetchDeepbookStatusEvent` which contains information about the Deepbook status, including price data, price ranges, and pagination details. The package provides two entry functions, `fetch_deepbook_status_bid_side` and `fetch_deepbook_status_ask_side`, which query the Deepbook CLOB (Central Limit Order Book) for bid and ask side order book data, respectively. These functions take a `Pool` object, limits for price ranges and data points, optional pagination parameters (next tick level and order ID), and a `Clock` object. They calculate price ranges and aggregate depth within those ranges, then emit a `FetchDeepbookStatusEvent` containing the fetched data and pagination information. The functions perform input validation on the provided limits and use helper functions to calculate check points and sum depth.
area + brightness = call volume; hover for detail
{
"wallet": "0xdbf4cb94558679ef5e257a83f6e7d5d999432b7295f9d599e11ce7ed27f639b5",
"n_tx": 1601,
"n_successful_tx": 877,
"n_distinct_epochs": 126,
"n_distinct_sponsors": 0,
"first_seen_cp": 1579918,
"last_seen_cp": 69233604,
"first_seen_ts_ms": 1683128868331,
"last_seen_ts_ms": 1729002356382,
"total_gas_spent_mist": 4900243796,
"n_self_sponsored_tx": 1601,
"n_sponsored_tx": 0,
"gas_price_p50": 825,
"gas_price_p95": 950,
"active_hours_top24": [
7,
8,
11,
6,
3,
12,
9,
2,
10,
13,
4,
14,
16,
15,
5,
1,
20,
19,
18,
0,
22,
23,
17,
21
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.