You can refetch the query according to your specific requirements. For instance, using useSuiClientQuery, you can query transaction blocks while filtering based on certain conditions like account addresses or specific module functions:

const { data, isPending, error, refetch, isFetched } = useSuiClientQuery(
    "queryTransactionBlocks",
    {
      order: "descending",
      options: QUERY_OPTIONS,
      filter: QUERY_FILTER({
        FromAddress: account?.address || "",
        MoveFunction: {
          function: "your_package_function",
          module: "your_module",
          package: process.env.NEXT_PUBLIC_PACKAGE_ID!,
        },
      }),
    },
  );

Absolutely! The Sui SDK provides WebSocket subscriptions that are ideal for this. You can use sui_subscribeEvent and filter for Transfer events, specifically by the recipient address matching your wallet accounts. This will give you real-time notifications for incoming coins and objects, allowing you to detect deposits and update balances efficiently without needing a full-blown indexer. For balance accuracy, you can then call sui_getBalances after an event.

You can periodically use the sui_queryTransactions RPC method, filtering by your wallet's ToAddress and FromAddress to find relevant transactions since your last check. This is generally the most robust approach without a full indexer. While sui_subscribeTransaction exists for live updates, it's less reliable for critical balance tracking due to potential missed events on disconnects. For specific contract-based deposits that emit events, you could monitor those using sui_queryEvents or sui_subscribeEvent.

You can query any SUI package by events or by transactions using methods like getEvents or getTransactionBlocks with the SUI SDK. This approach allows you to filter events by parameters such as FromAddress, SenderAddress, or MoveFunction.