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: a18df5981b5998506dbeaf96d5a44e8bcc5ea358f1b06bf3f1c61c105e89708a
Tx prefix hash: f5ae147c9cebdc33c22fd6f37a9fa5e3fdbaf56e28147db25cf86564d0526341
Tx public key: 5c2374a25cf2bd44e450f6a56355efe67151c834afa110fa412e6d7d68251dfa
| Timestamp: 1780836422 | Timestamp [UTC]: 2026-06-07 12:47:02 | Age [y:d:h:m:s]: 00:001:15:46:00 |
| Block: 7412 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 617 | RingCT/type: yes/0 |
| Extra: 015c2374a25cf2bd44e450f6a56355efe67151c834afa110fa412e6d7d68251dfa020900000001e49593ff00 | ||
1 output(s) for total of 34.690526393253 HMNY
| stealth address | amount | amount idx | tag |
| 00: b12ff0b907ee9498d8fa6b403be81437559668d7dc613da40cbe03aefed7bb6f | 34.690526393253 | 9126 of 0 | <4a> |
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": 7472,
"vin": [ {
"gen": {
"height": 7412
}
}
],
"vout": [ {
"amount": 34690526393253,
"target": {
"tagged_key": {
"key": "b12ff0b907ee9498d8fa6b403be81437559668d7dc613da40cbe03aefed7bb6f",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 92, 35, 116, 162, 92, 242, 189, 68, 228, 80, 246, 165, 99, 85, 239, 230, 113, 81, 200, 52, 175, 161, 16, 250, 65, 46, 109, 125, 104, 37, 29, 250, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}