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: 5c1964eabfe772e2591290779ffac0d01ba4671d7d04e9bd2973be20aba213cd | ? | 5239 of 4191163 |
01: 117f327474497920cb9e8729eb5b37e35f223f05be13dfbc516166b6311c66a9 | ? | 5240 of 4191163 |
02: 3d14a307bafc268bb6b4e58bd8ed9f75264377337524580b6965144b7b86dfd0 | ? | 5241 of 4191163 |
03: 15b407290e2b2e9e9fbf935cdaf94adc1d749d673f8697316ce34dd4aecc37cb | ? | 5242 of 4191163 |
04: 0eed49a1eb8ce87cbea562174ce3533ef157a3b90878d7d61168e4118bf17d2b | ? | 5243 of 4191163 |
05: 927729f7a787bd47d7fb26f8e267b7141e886a24f947944594e76bc868fddff9 | ? | 5244 of 4191163 |
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: eb6aea3b9ce8a8b2154e4d410c4c7fb81317d2aa988432ad22fe22ae28a75a22 | 00000320 |
- 01: c4fd3691083e32feb50421227691684a9fc0742f37c59cd733b08dbb9e497ebf | 00000465 |
- 02: 5c1b188b25b24ed3df3133826c4ee59fcef0ad3ae6b25eeb55b79a4176416e4a | 00000491 |
- 03: 7a56d49bd9f7714b06444c4f766c78976e08238a95abcb0f522b638d2d372c0b | 00000495 |
- 04: 8f9b39bfd6aec794c390f1fd6e0f2f1ef70216d158b43667d60dba57db17c9ba | 00000501 |
- 05: 315bb18da849dbb808a5f6b6ca98ff43d4c4b16250a4a7271094531047e457a4 | 00000554 |
- 06: ef67a53f78289dfae41f314e4316f558496c45d30cc188a60c2db05a9cbb2472 | 00000558 |