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: 550f624cb5383063af6ca8142a3c77ca0323ee6fea5113f3bc2134622b5e7a25 | ? | 3587 of 4194614 |
01: bc4a54e21df7739666d96e618e2551626c6a826448eb571f250e3f01aa49ee5d | ? | 3588 of 4194614 |
02: eaf00417e51508935503a9bc5cea04b33c2588fe9267268fae128743579242fc | ? | 3589 of 4194614 |
03: e5280e1472e1624ac997c236d7886e4c3fce7845075135020b2030c6eeefbe90 | ? | 3590 of 4194614 |
04: 9bd6467156e63433b91aec3a6195462681d39b98f88e88da8a4a2f94fa8c51fa | ? | 3591 of 4194614 |
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: 8a78f93ed8793378c0d7be7a917a99458a8e197c388b30cc486456b4b8f35bc5 | 00000293 |
- 01: d5a7daf436365786d83e3f789c57a742551434c1ce3af0c4ef338e0d9d50b82c | 00000317 |
- 02: 2a71e4affdda6e4242ebc368f8431ba2de69d09baf4ff41a4e0b72fde77a09a9 | 00000468 |
- 03: 913578a3f6c559fcedd4fb41f4dc8e5ca9f0b5ca0187e105a3ec4257d785bb77 | 00000479 |
- 04: f75f00dd1a8133144cec44ce5d4a0a46cb28151473703a79422a9ab4fda82fce | 00000486 |
- 05: a7ea980f0ff767a92839e8b8d9f3ce272f79dfeda4cdfc8132fa100c04ed7f77 | 00000493 |
- 06: 1c22a1c009016cc64f31c326edc188c5d750caa636490e531ef742534fe16fb2 | 00000496 |