Indexer Queries needed for new functionality

[gregnazario]

• Modules by modification time, allows for historical code data
• Transactions by coin type and owner, with full information, allows for all coin transactions for a user
• Coin / FA Refs, tells if a coin can be minted or burned or frozen or dispatchable
• Object refs, tells if an object can be transferred, or deleted, or extended

[gregnazario]

@cursoragent do you know if you can add modules by modification time, have historical lookups for modules?

[cursor]

The implementation is complete and fully tested. Here's a summary of what was done:

New hook: useGetModulePublishHistory queries the indexer for package publish transactions (0x1::code::publish_package_txn) ordered by version/time, returning version numbers, timestamps, and sender info for any account.

Updated hooks — useGetAccountModules, useGetAccountModule, useGetAccountResource, and useGetAccountPackages all now accept an optional ledgerVersion parameter, enabling fetching historical module state at any point in the blockchain's history.

New UI component: ModuleVersionSelector — a dropdown above the module tabs that lists all historical publish versions with timestamps. When a historical version is selected, a warning chip appears and the Packages/Code tabs load data from that point in time. Users can easily return to the latest version.

Testing confirmed the feature works end-to-end on mainnet — historical versions correctly showed different module states (e.g., an older version had fewer packages/modules than the current version), proving the historical lookup is accurate.

  

[gregnazario]

@cursoragent in a different PR can you add the transactions by type and owner

[cursor]

Here's a summary of what was implemented:

New feature: Transactions by coin type and owner (PR #1500)

• Created useGetCoinActivitiesByOwner hook that queries the indexer's fungible_asset_activities table filtered by both asset_type and owner_address
• Updated both the Coin and FungibleAsset transaction tabs to support an ?owner= search parameter with a text input for manual filtering and a chip displaying the filtered owner
• Added a "Txns" column with receipt icon buttons in the Account CoinsTable, linking directly to the coin's transactions page with the owner pre-filled
• Fixed the existing useGetCoinActivities hook by removing the fungible_asset_activities_aggregate field (not available in the current indexer schema) and switching to prev/next pagination

The feature was tested end-to-end on mainnet, confirming that clicking the TXNS icon from an account's coins table correctly navigates to and loads the filtered transaction view.

  

[gregnazario]

@cursoragent can you get Coin / FA Refs, tells if a coin can be minted or burned or frozen or dispatchable working so it can be displayed on the coin / fungible asset page? These can only be created in the same transaction the coin is created

[cursor]

Here's a summary of what was implemented and tested:

New feature: FA Properties (Coin/FA Refs) display on Info tabs

• Created useGetFaProperties hook that fetches all resources at the FA metadata object address and detects capabilities:
  • Paired coins: Checks 0x1::coin::PairedFungibleAssetRefs for mint_ref_opt, burn_ref_opt, transfer_ref_opt
  • Custom FAs: Deep-scans resource data for fields matching ref patterns (mint_ref, burn_ref, transfer_ref, freeze_ref)
  • Dispatchable: Detects 0x1::fungible_asset::DispatchFunctionStore
  • Untransferable: Detects 0x1::fungible_asset::Untransferable
• Created FaPropertiesDisplay component showing properties as colored chip badges with tooltips
• Integrated into both Coin and FA Info tabs
• Added 11 unit tests covering all detection paths

Testing results (mainnet data):

• APT: Mintable, Burnable, Freezable enabled; Dispatchable disabled (correct -- APT is explicitly excluded from dispatch)
• USDT: All four properties enabled (correct -- USDT uses dispatch functions)

  

[gregnazario]

@cursoragent Can you do Object refs, tells if an object can be transferred, or deleted, or extended in a separate PR

These also can only be created in the same transaction that the object is created. Would be good to show on the object tab

[cursor]

The implementation is complete and fully tested. Here's a summary:

New feature: Object Capabilities on the Info tab

• Created useGetObjectRefs hook that finds an object's creation transaction via the indexer and scans its write set changes for TransferRef, DeleteRef, and ExtendRef patterns
• Added an "Object Capabilities" section to the Info tab showing colored chips ("Exists" in green / "Not Created" outlined) for each ref type, plus a link to the creation transaction
• Handles nested ref patterns including the AptosToken burn_ref.self pattern for DeleteRef detection using full ancestor key path tracking
• Added 17 unit tests covering direct fields, Option-wrapped refs, AptosToken nested patterns, edge cases, and transaction-level detection
• Added descriptive tooltips for all new fields

Verified end-to-end on mainnet:

• Framework object (0xa): All refs "Not Created" (genesis object)
• Token NFT objects: All refs "Not Created" (standard NFTs)
• ANS Domain Object: ExtendRef shows "Exists" (green), others "Not Created"