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: 9d911135e68f6941cecab69a85d01aaac671cd18f31753f0bf6ecd265651147a
Tx prefix hash: b526f15032fc83ce50229d5dd0e03a9d80c65f2a94093823ce8cd9dfff26fdbc
Tx public key: 974798930786fb1000aab75009458ec16900c766e101cce772035c4a6baf7d1b
| Timestamp: 1779434536 | Timestamp [UTC]: 2026-05-22 07:22:16 | Age [y:d:h:m:s]: 00:017:18:13:41 |
| Block: 92 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7794 | RingCT/type: yes/0 |
| Extra: 01974798930786fb1000aab75009458ec16900c766e101cce772035c4a6baf7d1b020900000001a662ed0300 | ||
1 output(s) for total of 35.178265706452 HMNY
| stealth address | amount | amount idx | tag |
| 00: 19071c53337d7c6545350626997ac2f930d17295e2006cebf19780758e7e494e | 35.178265706452 | 88 of 0 | <55> |
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": 152,
"vin": [ {
"gen": {
"height": 92
}
}
],
"vout": [ {
"amount": 35178265706452,
"target": {
"tagged_key": {
"key": "19071c53337d7c6545350626997ac2f930d17295e2006cebf19780758e7e494e",
"view_tag": "55"
}
}
}
],
"extra": [ 1, 151, 71, 152, 147, 7, 134, 251, 16, 0, 170, 183, 80, 9, 69, 142, 193, 105, 0, 199, 102, 225, 1, 204, 231, 114, 3, 92, 74, 107, 175, 125, 27, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}