A block explorer, a testnet explorer and faucet, and a public node that light wallets can lean on. It all runs on hardware I own, so the network has one more independent operator keeping the lights on.
Free to use, no account needed. Everything on this page is for PIVX, and none of it asks for your keys.
Blocks, transactions, addresses, masternodes and governance, plus a full analytics suite. Built on RustyBlox, Liquid369's Rust explorer, indexing straight from a full node I run.
The same explorer pointed at the PIVX testnet, for checking what your code actually broadcast. Testnet coins have no value, so break things freely.
Paste a testnet address and get some tPIV to build with. The faucet's wallet stakes what it holds, so it earns new coins while it gives them away. There's a cooldown per address so one script can't drain it.
A read-mostly node API for light wallets like MyPIVXWallet, on mainnet and testnet. Wallets that don't run their own node have to ask someone else's, and right now very few people run one.
An experiment in HTTP 402 payments settled over PIVX. The endpoint answers
402 Payment Required, you pay the amount it quotes, and the
content unlocks. Very much a lab demo, not a production service.
Pure-Rust PIVX wallet primitives, Sapling shield included, that build for native apps and for the browser through WASM. It's a multi-chain fork of PIVX Labs' wallet kit, and the PIVX fixes I make go back upstream.
Point your wallet or script at these. The explorer speaks the Blockbook v2 API,
so anything that already talks to Blockbook only needs a new host. The node API
is the one MyPIVXWallet expects: GET /<method>?params=a,b.
The node API only answers a short list of methods: chain queries, masternode and budget lookups, and broadcasting a signed transaction. It holds no wallet you can reach, and it's rate limited, so a runaway loop hits the limit long before it hurts anyone else.
Rent a game server from ComputingCache and pay for it in PIVX. Checkout runs through my own BTCPay Server, so there's no payment processor in the middle and nobody asks for a card.
ComputingCache is an independent operator. None of this is run by, or speaks for, the PIVX Project; it's one community member's contribution to the network. The privacy policy covers what the explorer, node and faucet log, and the terms apply here like everywhere else on the site.