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: e4db6212ed903d7f38c1dceff6f7a61152bc971ebb2e5810daa8349851da97ca
Tx prefix hash: 05570fcb6d863d94e95ed8210e4043297c0acf1c5b432d6c9c79967dd5701979
Tx public key: 400e945e3c251f4c26b548310f91da79d6d113663bc339cfff8ba8d088c34c34
| Timestamp: 1779637070 | Timestamp [UTC]: 2026-05-24 15:37:50 | Age [y:d:h:m:s]: 00:016:01:31:13 |
| Block: 1147 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7587 | RingCT/type: yes/0 |
| Extra: 01400e945e3c251f4c26b548310f91da79d6d113663bc339cfff8ba8d088c34c34020900000002ba6d17be00 | ||
1 output(s) for total of 35.107549248633 HMNY
| stealth address | amount | amount idx | tag |
| 00: c895f004cc5d07b79c140c75eed2ac731ad91ebc1216505e5046ee4073a1513f | 35.107549248633 | 1289 of 0 | <4d> |
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": 1207,
"vin": [ {
"gen": {
"height": 1147
}
}
],
"vout": [ {
"amount": 35107549248633,
"target": {
"tagged_key": {
"key": "c895f004cc5d07b79c140c75eed2ac731ad91ebc1216505e5046ee4073a1513f",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 64, 14, 148, 94, 60, 37, 31, 76, 38, 181, 72, 49, 15, 145, 218, 121, 214, 209, 19, 102, 59, 195, 57, 207, 255, 139, 168, 208, 136, 195, 76, 52, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}