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: c9dc0cdfffb5bb915c65a4263a6bd4fc40a93b8fa6a9b48848f42b4804a51f79
Tx prefix hash: ffc5494ab902f32d2909bac2f596352a34b79a2538fda2fe47e424b1e658c723
Tx public key: ec2dbe9d45a6cb57002a8b055f4cb9a1c0d937c4e475ebd313f8bf067f3f1e27
| Timestamp: 1780323359 | Timestamp [UTC]: 2026-06-01 14:15:59 | Age [y:d:h:m:s]: 00:007:10:30:48 |
| Block: 5118 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2768 | RingCT/type: yes/0 |
| Extra: 01ec2dbe9d45a6cb57002a8b055f4cb9a1c0d937c4e475ebd313f8bf067f3f1e2702090000005726697be300 | ||
1 output(s) for total of 34.842646025182 HMNY
| stealth address | amount | amount idx | tag |
| 00: efe3052cce6b465ab1626e4fc7dbcfea788e5867605db0da611a2fd2291d95cf | 34.842646025182 | 6493 of 0 | <4f> |
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": 5178,
"vin": [ {
"gen": {
"height": 5118
}
}
],
"vout": [ {
"amount": 34842646025182,
"target": {
"tagged_key": {
"key": "efe3052cce6b465ab1626e4fc7dbcfea788e5867605db0da611a2fd2291d95cf",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 236, 45, 190, 157, 69, 166, 203, 87, 0, 42, 139, 5, 95, 76, 185, 161, 192, 217, 55, 196, 228, 117, 235, 211, 19, 248, 191, 6, 127, 63, 30, 39, 2, 9, 0, 0, 0, 87, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}