Providers
ar.io
Arweave through ar-io.dev, the gateway the AR.IO team runs itself. The fallback behind Turbo. No key.
Provider
ar.io
- arweave
- Chains
- 1
- Auth
- none
- Operations
- 4 of 10
served 4 / 10
Operations
- balance
getBalanceserved - history
getTxHistoryserved - tx detail
getTxDetailserved - utxos
getUtxosabsent - pubkey
getPubkeyabsent - contract
getContractInfoabsent - tokens
getTokenBalancesabsent - transfers
getTokenTransfersabsent - gas
getGasDataabsent - block
getBlockInfoserved
Access
- Create
create("ario") - Import
@agntn/explorers/providers/ario - Host
ar-io.dev - Statusproviders on the docs worker
Address it
import { Ario } from "@agntn/explorers/providers/ario";
const ario = new Ario(); // or create("ario")
await ario.getTxDetail("mILC0VAVV4cGR8tVlzMEb2GgE_Krfi2yGRV8rrSNgDc", "arweave");
That's a data item bundled around block 1,700,000. Turbo doesn't know it. ar-io.dev does, bundle id included.
Why second?
It knows the old layer 1 transfers too, and some old uploads Turbo lost. But it once ran past the 15-second timeout on a tag filter Turbo answered in under a second. So it waits behind Turbo and takes over when Turbo falls over. Digging through uploads from that era? Name ario yourself.
Gotchas
- It's the same class as arweave.net, only the default gateway differs. Windows, tags, fees and pending rows behave as listed there.
Where it lives
src/providers/ario.ts, on top of src/providers/arweave.ts.