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: 752f21f194de8dc8fca9f2d7f224edafe80575890d78a08d4a39ab3a4b9e8431
Tx prefix hash: cf20dbbada40ad97c268cd562b3e7896610d4dd8c67e5f493781209c89e4fae4
Tx public key: a85f6f74ac6a532cbf977a7792580c5abcca13b4f6df51e2b769bfcace1be7e9
| Timestamp: 1780028526 | Timestamp [UTC]: 2026-05-29 04:22:06 | Age [y:d:h:m:s]: 00:010:20:24:41 |
| Block: 4183 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3703 | RingCT/type: yes/0 |
| Extra: 01a85f6f74ac6a532cbf977a7792580c5abcca13b4f6df51e2b769bfcace1be7e902090000000726697be300 | ||
1 output(s) for total of 34.904838887981 HMNY
| stealth address | amount | amount idx | tag |
| 00: 318b927b18606f14b68b328467777ea3c6d51eec4ea20ed2f73bf956ddeea672 | 34.904838887981 | 5216 of 0 | <37> |
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": 4243,
"vin": [ {
"gen": {
"height": 4183
}
}
],
"vout": [ {
"amount": 34904838887981,
"target": {
"tagged_key": {
"key": "318b927b18606f14b68b328467777ea3c6d51eec4ea20ed2f73bf956ddeea672",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 168, 95, 111, 116, 172, 106, 83, 44, 191, 151, 122, 119, 146, 88, 12, 90, 188, 202, 19, 180, 246, 223, 81, 226, 183, 105, 191, 202, 206, 27, 231, 233, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}