Providers
Aptos Explorer
Registered, honest and empty. Aptos Explorer has no documented account API, so every operation throws UnsupportedOperationError.
Provider
Aptos Explorer
- aptos
- Chains
- 1
- Auth
- none
- Operations
- 0 of 10
served 0 / 10
Operations
- balance
getBalanceabsent - history
getTxHistoryabsent - tx detail
getTxDetailabsent - utxos
getUtxosabsent - pubkey
getPubkeyabsent - contract
getContractInfoabsent - tokens
getTokenBalancesabsent - transfers
getTokenTransfersabsent - gas
getGasDataabsent - block
getBlockInfoabsent
Access
- Create
create("aptos") - Import
@agntn/explorers/providers/aptos - Host
none - 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")returnsaptos, and any read then throwsUnsupportedOperationErrornaming 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.