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: f533c15ac638cc9c38dbede3aaae5254ae5ea59076ddda53a3a7280465d22f22
Tx prefix hash: 2374ba81e6b89bcb8771e678ed5dd2beb1444deffb56748ee5d1dd11a0d96d13
Tx public key: 3569968969924c364f1deecf74a900992a15b02b7a470b40ac12584c8340699a
| Timestamp: 1779629248 | Timestamp [UTC]: 2026-05-24 13:27:28 | Age [y:d:h:m:s]: 00:015:15:05:34 |
| Block: 820 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7209 | RingCT/type: yes/0 |
| Extra: 013569968969924c364f1deecf74a900992a15b02b7a470b40ac12584c8340699a020900000001ba6d17be00 | ||
1 output(s) for total of 35.129452783354 HMNY
| stealth address | amount | amount idx | tag |
| 00: e7014dfea6bfea9eed1e296ba25818f2920fad7a00cdccc9b17bed49b0592d12 | 35.129452783354 | 952 of 0 | <e7> |
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": 880,
"vin": [ {
"gen": {
"height": 820
}
}
],
"vout": [ {
"amount": 35129452783354,
"target": {
"tagged_key": {
"key": "e7014dfea6bfea9eed1e296ba25818f2920fad7a00cdccc9b17bed49b0592d12",
"view_tag": "e7"
}
}
}
],
"extra": [ 1, 53, 105, 150, 137, 105, 146, 76, 54, 79, 29, 238, 207, 116, 169, 0, 153, 42, 21, 176, 43, 122, 71, 11, 64, 172, 18, 88, 76, 131, 64, 105, 154, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}