QRDXDocs

Transaction history

What an account did and received, and the chain's latest transactions, from the node's index.

Every node indexes each canonical block's transactions under every account they touched, with that account's roles: legacy transfers, exchange operations (token moves, swaps, orders, pools, perps, NFTs, staking) and EVM transactions with the token transfers they emitted. An account's 0x and 0xPQ forms share one history.

RESTJSON-RPC
GET /get_address_history?address=&limit=50&cursor=&kinds=tx_getHistory(address, limit, cursor, kinds)an account's transactions, newest first
GET /get_latest_transactions?limit=&cursor=&kinds=tx_getRecent(limit, cursor, kinds)the chain's latest transactions
GET /get_indexed_transaction?tx_hash=tx_getTransaction(tx_hash)one transaction and every account it touched
JS
An account's transactions
output⌘/Ctrl + Enter to run
Edit the code and run it. It talks to testnet from your browser.

Fields

Each entry has tx_hash, kind (transfer, exchange, evm, genesis, coinbase), op (e.g. SWAP), block_height, timestamp, sender, target, asset, amount, status (success, failed, unknown), fee (QRDX), error, detail (parameters and what it did) and the account's roles:

RoleMeaning
senderit sent the transaction
to, fromthe recipient or source of a transfer
spender, operator, accountan allowance spender, an operator, an affected account
makerits resting order was filled by someone else's transaction
token_from, token_toa token transfer's source or recipient
createdthe transaction created it (a token, a pool)

Paging

Pass the previous page's next_cursor as cursor. kinds filters (comma-separated). indexed_height says how far the index has got; it follows the chain within about a second of each block and follows reorganisations.

GET
/get_latest_transactions
https://test.qrdx.org/get_latest_transactions?limit=5&kinds=exchange

On testnet most exchange transactions are validators' ORACLE_VOTEs.

Run sends this request from your browser.

On this page