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: 895f8ccf346d64fa81d953e6c7e7b03884e0aa04fbe5e0ccda48e3c6ab4613a6 | 0.080000000 | 1236 of 1497 |
| 01: 0b976da40d4d0fdd15a9c7296c53eb9fec4f602c502f6a0a9f6a9405e33e6a10 | 0.600000000 | 847 of 1091 |
| 02: 7fb34a1e133de3f8f30667b67a93c5c2977b76f03360d936f481127e084bb9bd | 9.000000000 | 11927 of 12603 |
| 03: 56764616d2292f2e46416316673a808ea6fda48cc9ea8c3cf681dff2dd909359 | 10.000000000 | 11927 of 12603 |
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
{
"version": 1,
"unlock_time": 60994,
"vin": [ {
"gen": {
"height": 60976
}
}
],
"vout": [ {
"amount": 80000000,
"target": {
"key": "895f8ccf346d64fa81d953e6c7e7b03884e0aa04fbe5e0ccda48e3c6ab4613a6"
}
}, {
"amount": 600000000,
"target": {
"key": "0b976da40d4d0fdd15a9c7296c53eb9fec4f602c502f6a0a9f6a9405e33e6a10"
}
}, {
"amount": 9000000000,
"target": {
"key": "7fb34a1e133de3f8f30667b67a93c5c2977b76f03360d936f481127e084bb9bd"
}
}, {
"amount": 10000000000,
"target": {
"key": "56764616d2292f2e46416316673a808ea6fda48cc9ea8c3cf681dff2dd909359"
}
}
],
"extra": [ 1, 173, 40, 76, 236, 62, 64, 102, 75, 201, 14, 220, 207, 80, 238, 249, 187, 9, 211, 97, 109, 110, 150, 40, 84, 9, 77, 205, 241, 208, 242, 56, 221, 3, 33, 0, 209, 71, 161, 158, 88, 85, 33, 195, 159, 1, 113, 82, 203, 133, 45, 46, 231, 166, 209, 255, 67, 166, 177, 222, 253, 125, 193, 230, 97, 56, 117, 8, 2, 16, 0, 0, 0, 8, 148, 57, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0
],
"signatures": [ ]
}