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: c3cddf2cde8dadca9dab6787cc4f44510ab77a533d28786a2ef287647ba2f0ce
Tx prefix hash: 05d28d7c32f13963fec23554c4b6d5411e5080059d0b75070a984fa08faf58e3
Tx public key: a87a30c747de9ba3fe4aabf177323cce9f4d29312bbf72c4c03c4b1538889c37
| Timestamp: 1780986244 | Timestamp [UTC]: 2026-06-09 06:24:04 | Age [y:d:h:m:s]: 00:000:08:24:51 |
| Block: 8144 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 495 | RingCT/type: yes/0 |
| Extra: 01a87a30c747de9ba3fe4aabf177323cce9f4d29312bbf72c4c03c4b1538889c37020900000001e49593ff00 | ||
1 output(s) for total of 34.642125951442 HMNY
| stealth address | amount | amount idx | tag |
| 00: 865d04f9c513f8ff86470aedd6b73fdcdbae9e07498bac4285b0341f1b5e0101 | 34.642125951442 | 10086 of 0 | <95> |
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": 8204,
"vin": [ {
"gen": {
"height": 8144
}
}
],
"vout": [ {
"amount": 34642125951442,
"target": {
"tagged_key": {
"key": "865d04f9c513f8ff86470aedd6b73fdcdbae9e07498bac4285b0341f1b5e0101",
"view_tag": "95"
}
}
}
],
"extra": [ 1, 168, 122, 48, 199, 71, 222, 155, 163, 254, 74, 171, 241, 119, 50, 60, 206, 159, 77, 41, 49, 43, 191, 114, 196, 192, 60, 75, 21, 56, 136, 156, 55, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}