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: d9b0659fdb9f950d23e7920f019ddeafd8d5fdbeca85cb6345f4795da364b9c1
Tx prefix hash: dd6bd5e2e17084a974e353cae8a93d6e52e5ec30bd64208d16e004c88a487ff1
Tx public key: 469ba9d4943941a9378225b3079172e7e7b5a822e56cee06de7be77a0c9aa4fd
| Timestamp: 1779477179 | Timestamp [UTC]: 2026-05-22 19:12:59 | Age [y:d:h:m:s]: 00:017:06:22:58 |
| Block: 624 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7262 | RingCT/type: yes/0 |
| Extra: 01469ba9d4943941a9378225b3079172e7e7b5a822e56cee06de7be77a0c9aa4fd02090000000293369e7d00 | ||
1 output(s) for total of 35.145892857268 HMNY
| stealth address | amount | amount idx | tag |
| 00: d1ffe5571a8e1293ed0fccd57a48ae17575c996adbf8f5a7ffea96a0c06057c9 | 35.145892857268 | 649 of 0 | <e2> |
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": 684,
"vin": [ {
"gen": {
"height": 624
}
}
],
"vout": [ {
"amount": 35145892857268,
"target": {
"tagged_key": {
"key": "d1ffe5571a8e1293ed0fccd57a48ae17575c996adbf8f5a7ffea96a0c06057c9",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 70, 155, 169, 212, 148, 57, 65, 169, 55, 130, 37, 179, 7, 145, 114, 231, 231, 181, 168, 34, 229, 108, 238, 6, 222, 123, 231, 122, 12, 154, 164, 253, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}