1SELECT id, symbol, name, decimals, tx_count FROM base.uniswap_token
2ORDER BY tx_count DESC
3LIMIT 20;
4
5
6
7
8
9
10
11
12
13

1SELECT * FROM object  0x5617f3429da2b8bc698818fe0c57f05e4216623ab0975b7653405385134ad37e,0x5617f3429da2b8bc698818fe0c57f05e4216623ab0975b7653405385134ad378 
2ON sui_mainnet;
3
4/*
5Fetches full object details via Sui RPC using `sui_getObject` for the specified object IDs.
6These are raw on-chain Move objects from Sui's storage.
7This is useful for inspecting fields like `type`, `owner`, and custom content defined in the Move module.
8*/
9
10
11
12
13
14
15
16
17
18

1SELECT
2  id,
3  sender,
4  debts_count
5FROM sui.scallop_obligation
6LIMIT 20;
7
8
9
10
11
12
13
14
15

1SELECT * FROM object  0x5617f3429da2b8bc698818fe0c57f05e4216623ab0975b7653405385134ad37e,0x5617f3429da2b8bc698818fe0c57f05e4216623ab0975b7653405385134ad378 
2ON sui_mainnet;
3
4/*
5Fetches full object details via Sui RPC using `sui_getObject` for the specified object IDs.
6These are raw on-chain Move objects from Sui's storage.
7This is useful for inspecting fields like `type`, `owner`, and custom content defined in the Move module.
8*/
9
10
11
12
13
14
15
16
17
18

1SELECT
2  d.obligation_id AS obligation_id,
3  d.asset AS asset,
4  ROUND(CAST(d.amount AS BIGINT) / 1e9, 4) AS amount_sui,
5  TO_TIMESTAMP(CAST(d."timestampMs" AS BIGINT) / 1000) AS deposit_time,
6  o.debts_count AS linked_debts
7FROM sui.scallop_deposit d
8LEFT JOIN sui.scallop_obligation o
9  ON d.obligation_id = o.id
10WHERE CAST(d.amount AS BIGINT) > 0
11ORDER BY deposit_time DESC
12LIMIT 10;
13
14-- This query retrieves the 100 most recent deposits from the sui.scallop_deposit table, enriched with associated obligation data from sui.scallop_obligation.
15
16-- Key elements include:
17
18--     obligation_id: The ID tying the deposit to a specific obligation.
19
20--     asset: The deposited asset type (e.g., SUI).
21
22--     amount_sui: The deposit amount, converted from base units to readable SUI (using 1e9 divisor).
23
24--     deposit_time: Timestamp of the deposit (converted from milliseconds).
25
26--     linked_debts: Number of debt entries associated with the linked obligation (via LEFT JOIN).
27
28-- Only deposits with a positive amount are included, and results are sorted by the most recent deposit activity.
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49

1SELECT * FROM tx WHERE block = 45090 ON base;
2
3/*
4  Description:
5  This query fetches all transactions included in block number 45090 on the Base network.
6
7  Use Case:
8  Useful for analyzing activity within a specific block, such as:
9  - Identifying which contracts or accounts were interacted with
10  - Measuring block-level gas usage or throughput
11  - Auditing protocol behavior or tracing specific events
12
13  The result includes all available fields for each transaction, such as `from`, `to`, `value`, `gas_price`, `input`, `status`, etc.
14*/
15
16
17
18
19
20
21
22
23
24

1SELECT *
2FROM eth.uniswap_Pool
3WHERE created_at_timestamp = '2021-05-05 19:32:40';
4
5
6
7
8
9
10
11
12
13
14

1SELECT 
2  pool,
3  COUNT(*) AS total_swaps,
4  SUM(COALESCE(amount_in, 0)) AS total_volume_in,
5  SUM(COALESCE(amount_out, 0)) AS total_volume_out
6FROM sui.cetus_swap
7WHERE DATE(TO_TIMESTAMP("timestampMs" / 1000)) = '2025-05-21'
8GROUP BY pool
9ORDER BY total_swaps DESC
10LIMIT 10;
11
12
13
14
15
16
17
18
19
20

1SELECT balance, chain FROM account vitalik.eth ON eth, base 
2/* Fetches the balance and the chain for the account 'vitalik.eth' across Ethereum and Base.
3   You can use either an ENS name or a wallet address in place of 'vitalik.eth'. */
4
5/*
6  Notes:
7  - You can use either an ENS name (e.g. `vitalik.eth`) or a raw address (e.g. `0x...`) as the account identifier.
8  - This is useful for tracking an address's assets across multiple EVM-compatible chains.
9*/
10
11
12
13
14
15
16
17
18
19

1SELECT from,  to,value, gas_price, status  FROM tx 
2    0x6f93d4add2ef6cdfbb9f25b9895830d719dd8edf6637b639d5c33e808ded4247,
3    0xa9e39789f09753e7afa0838c52e3dd332627f1b18eec07e1652ede6f5a958fa1
4ON eth;
5
6/*
7  Description:
8  This query retrieves detailed transaction information for two specific transactions 
9  on the Base network.
10
11  Fields selected:
12  - `from`: Sender address of the transaction
13  - `to`: Recipient address (contract or user)
14  - `value`: Amount of ETH or token transferred
15  - `gas_price`: Price per unit of gas paid by the sender
16  - `status`: Whether the transaction succeeded or failed
17
18  Use Case:
19  Useful for auditing or tracking high-value or specific-purpose transactions 
20  such as contract deployments, token transfers, or protocol interactions.
21*/
22
23
24
25
26
27
28
29
30
31