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: 31c3ac16dd98e4e6dbe79bd91ffad0040a557423f0db90dce8cd314c3a81cca5 | ? | 5148 of 4192180 |
01: 16679686998456e61144af56f725d84e517c95210e7cf92b3b2d362666e111a8 | ? | 5149 of 4192180 |
02: 762b78bd3bba1fda1641394041b9f24de8232e830e9e4c9aabc802cbd1fc1275 | ? | 5150 of 4192180 |
03: fd571c8e206ad3e0ab93eeeeb02f5059b52cf68bc7f93c7ce36b268e48e478e2 | ? | 5151 of 4192180 |
04: 0dd5d3a011aa8fb58f4cb79b40fffb595097a374ad71221c43dc84ab64581711 | ? | 5152 of 4192180 |
05: b65668bdfcae82d133482b0943589034685f2bf23db82d35270af44ab08f04ca | ? | 5153 of 4192180 |
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: b0b6821d4316ae77aecb601e86de4b85effa109e665d478112f28269af216395 | 00000478 |
- 01: 96f59635abfd456ed710f85b91ca62f933635ba0c507d822190153dbb77a47fe | 00000482 |
- 02: a96426d97e489a4ee2efe72af47f964a65acf1104b72082d72fe4547bf9ea81f | 00000499 |
- 03: d618f3c2bea9b30b8c938bb41f03059d8ce80626d94f95bee77759c53760114f | 00000505 |
- 04: df01d679580cfae8d122969668406d2489f54d59fae581696bcb30a6c6da2bfa | 00000511 |
- 05: 55ba2b29c7380ed0b11178ebce832a4ade963395c953650c733e464e47181f78 | 00000525 |
- 06: aa199e934a18280dba321d44846f135d69a0e6ab06c614ed07f56797f4471469 | 00000553 |