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: 75a284841c81fad9146a41cfcbda7821ce345f84b3b8fa39a73c43dd8f390ab3
Tx prefix hash: 22d07367667c9fdcbd9485b044f7e3f67e5fb9a7447ceb49f4796c9fcc726261
Tx public key: 5a53bfedec30c75a14e442d91bf152852690c93028200c7adb8ae50c2bd87f61
| Timestamp: 1779956255 | Timestamp [UTC]: 2026-05-28 08:17:35 | Age [y:d:h:m:s]: 00:011:17:18:22 |
| Block: 3695 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4191 | RingCT/type: yes/0 |
| Extra: 015a53bfedec30c75a14e442d91bf152852690c93028200c7adb8ae50c2bd87f6102090000000726697be300 | ||
1 output(s) for total of 34.937342983819 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5670e3c62e7abc0c41ad968c399bf666d95e544a6faee257467919e3aca421c2 | 34.937342983819 | 4468 of 0 | <b9> |
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": 3755,
"vin": [ {
"gen": {
"height": 3695
}
}
],
"vout": [ {
"amount": 34937342983819,
"target": {
"tagged_key": {
"key": "5670e3c62e7abc0c41ad968c399bf666d95e544a6faee257467919e3aca421c2",
"view_tag": "b9"
}
}
}
],
"extra": [ 1, 90, 83, 191, 237, 236, 48, 199, 90, 20, 228, 66, 217, 27, 241, 82, 133, 38, 144, 201, 48, 40, 32, 12, 122, 219, 138, 229, 12, 43, 216, 127, 97, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}