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: 93e4c86118df265afeea324a9cd9ef49a80760370deb69e7c1cf3a8d7af614a8 | ? | 44009 of 4277539 |
01: add25930e66aff2658edb5473d5680e42d7374fa410228c71758ccbed7760bcd | ? | 44010 of 4277539 |
02: 10d217132573a9da1737d30a206b7ee1fb0d63d5b5fcac4afa5a7a8dc87e92fd | ? | 44011 of 4277539 |
03: 51b50bc0f27f95334079d96fb379c689c4a4e60be3a3e7d3b817773cc84efed6 | ? | 44012 of 4277539 |
04: 1030bc10119171eb274fd06348f06a70bff7a93b07d191d889c61cf5569fa276 | ? | 44013 of 4277539 |
05: 5809ef33770269bb05646e77e30a452cb25dbeb56d04981a1211324281db1cd6 | ? | 44014 of 4277539 |
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: d7e4c16a01027e1a33f11d3126d01ddba39cf91334b4562c42bfd4a079d52144 | 00001367 |
- 01: 5ae79191455f7d9ea361adb4d69be69e2529d641007adf335f5f2dab9766ff6b | 00001542 |
- 02: 19d5c8ef160d46e7da76d1ba3914db24207c1f1651a7040ccddd6eed27af1061 | 00001636 |
- 03: ddb1d00ead5a7f286ce34bba094e6204c86cbe9ac126eb8a5541f53584242968 | 00001807 |
- 04: 5ab77d5a255b678e5a8d32d0fc73d7ab086e41a1f549a9e92bc104e879103099 | 00001831 |
- 05: be2a35d568248dd6d32a4c2d4925454cbbac7f6070a42772d2bd5b687ace155e | 00002001 |
- 06: 1e497077ea76c5c2d6a134f89969dae84cf0dd5bc12070f54db29fb5a26e662a | 00002075 |