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: cde23fc60088634aade909c1af4c9c7b6299584d4a0e6d503f76052f718b03b8
Tx prefix hash: 08d062710ffaf399db6b43eef17db3b6b59fd8d75264951b348e31ea3c842f9f
Tx public key: 5b22d12aa5ce1270f9752f8eb56318c9d5a3fd892f6086cd205b56b3ffc08323
| Timestamp: 1780799573 | Timestamp [UTC]: 2026-06-07 02:32:53 | Age [y:d:h:m:s]: 00:001:20:46:00 |
| Block: 6814 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1072 | RingCT/type: yes/0 |
| Extra: 015b22d12aa5ce1270f9752f8eb56318c9d5a3fd892f6086cd205b56b3ffc08323020900000001e49593ff00 | ||
1 output(s) for total of 34.730116828030 HMNY
| stealth address | amount | amount idx | tag |
| 00: f42195e210070d5e78e81e2d707628821515556c2bda6bd2ccbfa9a2504eb1f3 | 34.730116828030 | 8414 of 0 | <25> |
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": 6874,
"vin": [ {
"gen": {
"height": 6814
}
}
],
"vout": [ {
"amount": 34730116828030,
"target": {
"tagged_key": {
"key": "f42195e210070d5e78e81e2d707628821515556c2bda6bd2ccbfa9a2504eb1f3",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 91, 34, 209, 42, 165, 206, 18, 112, 249, 117, 47, 142, 181, 99, 24, 201, 213, 163, 253, 137, 47, 96, 134, 205, 32, 91, 86, 179, 255, 192, 131, 35, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}