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: 14642a46e8fc734e0c6bf96723cab19b32329ab326197c7d448e1e024144ad3e
Tx prefix hash: 030c299725f74b3bc838b6b3ec2d17619e5c22d003837d3c52df2751f471d251
Tx public key: 35c0a492d26a3cf403195687e6d3aaad22fbc7af3db533a219ed1d666f3f329c
| Timestamp: 1779863333 | Timestamp [UTC]: 2026-05-27 06:28:53 | Age [y:d:h:m:s]: 00:012:20:20:55 |
| Block: 2711 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5188 | RingCT/type: yes/0 |
| Extra: 0135c0a492d26a3cf403195687e6d3aaad22fbc7af3db533a219ed1d666f3f329c02090000000226697be300 | ||
1 output(s) for total of 35.011976108569 HMNY
| stealth address | amount | amount idx | tag |
| 00: f06cbffade519d470847dbc79597a7db6eb25e2505cc8ee997a574eeadf16caa | 35.011976108569 | 3199 of 0 | <5d> |
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": 2771,
"vin": [ {
"gen": {
"height": 2711
}
}
],
"vout": [ {
"amount": 35011976108569,
"target": {
"tagged_key": {
"key": "f06cbffade519d470847dbc79597a7db6eb25e2505cc8ee997a574eeadf16caa",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 53, 192, 164, 146, 210, 106, 60, 244, 3, 25, 86, 135, 230, 211, 170, 173, 34, 251, 199, 175, 61, 181, 51, 162, 25, 237, 29, 102, 111, 63, 50, 156, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}