Providers

Aptos Explorer

Registered, honest and empty. Aptos Explorer has no documented account API, so every operation throws UnsupportedOperationError.
provider
create("aptos")
auth
none
chains
Aptos
capabilities
none
endpoint
none
default chain
aptos

Why it exists

create("aptos") works and capabilities is all false. getBalance and getTxHistory throw UnsupportedOperationError, the optional methods are absent. That is 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 dishonest, 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.

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.

@agntn/explorers·MIT license· Read-only. Addresses you type go to a public explorer API, never to a wallet.