For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 6aef6c7cd5db394db4caaa4df6e01f55ac96221d59169e8b62294cf1ba2b5d1c
Tx prefix hash: e2273ef5101b05b0536e58bf0dea865b0e94bcf681956ab47de078ba1b7f9c75
Tx public key: 30a10d35d6f5eaddf2c6ea5518b6537c8796ed5bd44a6e74fe6357a9901302de
| Timestamp: 1779719541 | Timestamp [UTC]: 2026-05-25 14:32:21 | Age [y:d:h:m:s]: 00:014:11:03:36 |
| Block: 1723 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6163 | RingCT/type: yes/0 |
| Extra: 0130a10d35d6f5eaddf2c6ea5518b6537c8796ed5bd44a6e74fe6357a9901302de020900000001ba6d17be00 | ||
1 output(s) for total of 35.069000085864 HMNY
| stealth address | amount | amount idx | tag |
| 00: 56b473f09674d5e0dc87e382ba3b4eb27a8ccf888d4cb62939db68e93c778f98 | 35.069000085864 | 1899 of 0 | <e7> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 1783,
"vin": [ {
"gen": {
"height": 1723
}
}
],
"vout": [ {
"amount": 35069000085864,
"target": {
"tagged_key": {
"key": "56b473f09674d5e0dc87e382ba3b4eb27a8ccf888d4cb62939db68e93c778f98",
"view_tag": "e7"
}
}
}
],
"extra": [ 1, 48, 161, 13, 53, 214, 245, 234, 221, 242, 198, 234, 85, 24, 182, 83, 124, 135, 150, 237, 91, 212, 74, 110, 116, 254, 99, 87, 169, 144, 19, 2, 222, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}