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: 9f6ce8b60167f85901fa1de8c073d641e5d1e045f6ff0c9caf8aaad9909a880e
Tx prefix hash: 6fb1f8d50721ba8059c56a9e58df7b25d45f0e7413014f94b32e772fc2e8609a
Tx public key: 1a873e08c8af902aba109465b4e9c2da7d5a974f5304bb5da4b91fa5c9e18eba
| Timestamp: 1779632460 | Timestamp [UTC]: 2026-05-24 14:21:00 | Age [y:d:h:m:s]: 00:015:11:14:57 |
| Block: 953 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6933 | RingCT/type: yes/0 |
| Extra: 011a873e08c8af902aba109465b4e9c2da7d5a974f5304bb5da4b91fa5c9e18eba020900000001ba6d17be00 | ||
1 output(s) for total of 35.120542357964 HMNY
| stealth address | amount | amount idx | tag |
| 00: 574d65871abf4b70fd801a747a54a0d6ce42d580d8c375fb67e61f2289d9155c | 35.120542357964 | 1089 of 0 | <9e> |
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": 1013,
"vin": [ {
"gen": {
"height": 953
}
}
],
"vout": [ {
"amount": 35120542357964,
"target": {
"tagged_key": {
"key": "574d65871abf4b70fd801a747a54a0d6ce42d580d8c375fb67e61f2289d9155c",
"view_tag": "9e"
}
}
}
],
"extra": [ 1, 26, 135, 62, 8, 200, 175, 144, 42, 186, 16, 148, 101, 180, 233, 194, 218, 125, 90, 151, 79, 83, 4, 187, 93, 164, 185, 31, 165, 201, 225, 142, 186, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}