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: 34484b371b85f64d400802f8e799a6cba2aabd0882ea6cf3f5d296d87e28a4f0
Tx prefix hash: ff7ca8b200cd94e63539249a48a0875534d14584ded50d62ecba757bf0f6ea7f
Tx public key: 9c2de3264e4ae9293e42b126499d58049f514a279b17a622b8d72810d77c6156
| Timestamp: 1780981283 | Timestamp [UTC]: 2026-06-09 05:01:23 | Age [y:d:h:m:s]: 00:000:10:58:21 |
| Block: 8036 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 655 | RingCT/type: yes/0 |
| Extra: 019c2de3264e4ae9293e42b126499d58049f514a279b17a622b8d72810d77c6156020900000001e49593ff00 | ||
1 output(s) for total of 34.649262751340 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff5641a5af07319d3f3cfad2405330bea9ce465757b8262901ef9d0297b081a9 | 34.649262751340 | 9962 of 0 | <ac> |
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": 8096,
"vin": [ {
"gen": {
"height": 8036
}
}
],
"vout": [ {
"amount": 34649262751340,
"target": {
"tagged_key": {
"key": "ff5641a5af07319d3f3cfad2405330bea9ce465757b8262901ef9d0297b081a9",
"view_tag": "ac"
}
}
}
],
"extra": [ 1, 156, 45, 227, 38, 78, 74, 233, 41, 62, 66, 177, 38, 73, 157, 88, 4, 159, 81, 74, 39, 155, 23, 166, 34, 184, 215, 40, 16, 215, 124, 97, 86, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}