Check which outputs belong to given ARQ address/subaddress and viewkey
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
stealth address | amount | amount idx |
---|---|---|
00: 20e96a88785b142aa87e764bfcd4f158b4436329ef56cf74316a3a1a57574045 | ? | 21108 of 4196060 |
01: c1826e3278fad9b16eaf2b7cba1ea383f7664fc9296a364ebf0f2bc4e1ca13f3 | ? | 21109 of 4196060 |
02: 632859893508df82a3495e7a89d663535c823cd739d64b6ff8ddb3a01e387547 | ? | 21110 of 4196060 |
03: 4014ca8d38b9eb22a57cfbfed7af68356f4ce739afcc553f6d2e83e1e16ff33c | ? | 21111 of 4196060 |
04: 2a0fedb1cd41c10482c5d659123c16fa9550cead65c501979b1de2dce99444a4 | ? | 21112 of 4196060 |
05: aa02f860db0bd05930dfcda60b121e606b0335588902111caaa5e53706ac4da4 | ? | 21113 of 4196060 |
Check which outputs belong to given ARQ address/subaddress and viewkey
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them ARQ in this transaction
Tx private key can be obtained using get_tx_key
command in arqma-wallet-cli
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
ring members | blk |
---|---|
- 00: d14bbd5d40b62fe6e2961231d6356fc8d422cb9614747ab6a99e6fd79bf54d23 | 00000720 |
- 01: 9b33a4989ebd12b0417076b53700e4adcb58c395df37581fcca58ac76664018e | 00000755 |
- 02: a9f5918ff7b317e273a99c183268739b166c573d0c66a49405339ead95828b7d | 00000872 |
- 03: d131f7a837a06aab0e398bc68a20c297f48550e331b8838e05776d1c07adedab | 00000889 |
- 04: dfb122f1d96cc7c351a7555d3c4606187b483d6b3bcaf188b445b164950d8b04 | 00000951 |
- 05: 4d547143b60d14e8e40d524ec33916394ca601c53d81fbac9aa782dcca7cce3d | 00000994 |
- 06: 1460ce1c7bb2c4086dcbb15891a45b752f3b194fbad8aacfdc17115491582bd1 | 00001044 |