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: 2f560a9651b346093fb824ef482b625b48793dcc9452b9b4a917930baee97170
Tx prefix hash: a47ef28bb6da9501b6d7bd84fe41dc08e30d589a53866bac927e9d46a2ce00a1
Tx public key: cfef791888ca0cefce9f2841a3c96aff9df70f16169b7b6e54f80414e9193c43
| Timestamp: 1781013151 | Timestamp [UTC]: 2026-06-09 13:52:31 | Age [y:d:h:m:s]: 00:006:04:21:56 |
| Block: 8606 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 139 | RingCT/type: yes/0 |
| Extra: 01cfef791888ca0cefce9f2841a3c96aff9df70f16169b7b6e54f80414e9193c43020900000002e49593ff00 | ||
1 output(s) for total of 34.611612897747 HMNY
| stealth address | amount | amount idx | tag |
| 00: c2610399deeccbd9d8917f9d06619cb0bb5f9e749bcf5ad30bc61aea57eea558 | 34.611612897747 | 10636 of 0 | <85> |
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": 8666,
"vin": [ {
"gen": {
"height": 8606
}
}
],
"vout": [ {
"amount": 34611612897747,
"target": {
"tagged_key": {
"key": "c2610399deeccbd9d8917f9d06619cb0bb5f9e749bcf5ad30bc61aea57eea558",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 207, 239, 121, 24, 136, 202, 12, 239, 206, 159, 40, 65, 163, 201, 106, 255, 157, 247, 15, 22, 22, 155, 123, 110, 84, 248, 4, 20, 233, 25, 60, 67, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}