Providers

Aptos Explorer

Registered, honest and empty. Aptos Explorer has no documented account API, so every operation throws UnsupportedOperationError.
IDaptos10 / 19keyless
Provider

Aptos Explorer

  • aptos
Chains
1
Auth
none
Operations
0 of 10
served 0 / 10

Operations

  • balancegetBalanceabsent
  • historygetTxHistoryabsent
  • tx detailgetTxDetailabsent
  • utxosgetUtxosabsent
  • pubkeygetPubkeyabsent
  • contractgetContractInfoabsent
  • tokensgetTokenBalancesabsent
  • transfersgetTokenTransfersabsent
  • gasgetGasDataabsent
  • blockgetBlockInfoabsent

Access

Createcreate("aptos")
Import@agntn/explorers/providers/aptos
Hostnone
Statusproviders on the docs worker

Why it exists

create("aptos") works and capabilities is all false. getBalance and getTxHistory throw UnsupportedOperationError, the optional methods are absent. That's the whole provider.

Aptos Explorer publishes no account or history API. A fullnode REST endpoint exists, but hiding one behind an explorer provider just to make the capability table look complete would be lying, and the library's rule is that explorer data stays explorer data. So the provider stays registered, so that a chain lookup names it and the error you get is the typed limitation rather than Blockscout's UnsupportedChainError. It's in the table so you don't ask why it isn't in the table.

What that means for you

  • resolveProvider(undefined, "aptos") returns aptos, and any read then throws UnsupportedOperationError naming the operation.
  • The Explorer lists Aptos and answers 422 on it.
  • A provider that reads Aptos through a documented explorer API would replace this one in builtins; see Custom providers.

Where it lives

src/providers/aptos.ts.