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: cd4b646ee96800a515f4e4bdd4bd99ea3a8461d27718b18753274d17f50004a7 | ? | 56730 of 4277459 |
| 01: f3b1e7e7fa83f6fb81c9d6c0c27e92c5db96a471aa00275790d101456425b5be | ? | 56731 of 4277459 |
| 02: 3b72900abc3bf40bd54704c2fab225a189b65ede0bb587f36c34f76a08dbd28e | ? | 56732 of 4277459 |
| 03: b0bc6169d45ba1498edc32a21a218e4f8b567491b36a869ea6a39a1b4dbe19e2 | ? | 56733 of 4277459 |
| 04: 5e5bac40c1f6c8ec047ea47f12975c24e3dd2e1ef2f5421326478c0f9ac91e2f | ? | 56734 of 4277459 |
| 05: dfd813d7df769438d819c49da22b043ea131c44a0060695775afa901ffff0078 | ? | 56735 of 4277459 |
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: 0d382b0ddae178e84770f563d14700ba600487e881d34ca86c0e05e3661d0c84 | 00001118 |
| - 01: 298f4b581d25dbc882417e6183f96be225513b3c0908ebb3924c8e2e2ba5bd4f | 00001250 |
| - 02: 0f14d112fa5fe700416b19d3fba3a393361816b38a728530bbcb9939b8e79283 | 00001624 |
| - 03: 59f6a8d13195539a09025183152e5b2f82f85e7236c60b22fc7151581556b056 | 00002596 |
| - 04: 518fb96e77bd2d38426c4dfa0534007f4a2d317a320061955e2831f9d1939e2d | 00002620 |
| - 05: f6d6e521f0f7aa8531ed96956b3d70dc93ca2482a62913d46986158a457ae7a2 | 00002758 |
| - 06: 1f3d047c841bcef63c57a13167f297bc136757f442aca5d21aab28b1c7fb1803 | 00002945 |