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: a3994df9197650206c0ee671cb19422a95e3dd0df29b5b9b12b0d20506df164b
Tx prefix hash: c804445143079ef4326768f6ce30be20f788bbee3fee77c876d1d523c254f36e
Tx public key: 54121bd3fde7f7547e8128b1b61b0997251d2edfa3f99b84dac1e2078cf13f66
| Timestamp: 1780994339 | Timestamp [UTC]: 2026-06-09 08:38:59 | Age [y:d:h:m:s]: 00:007:23:57:15 |
| Block: 8296 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 449 | RingCT/type: yes/0 |
| Extra: 0154121bd3fde7f7547e8128b1b61b0997251d2edfa3f99b84dac1e2078cf13f66020900000001e49593ff00 | ||
1 output(s) for total of 34.632084056635 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0377dcf206d17c816398ea9b6973cfc888aa0284522cca525f59a24783fe005a | 34.632084056635 | 10264 of 0 | <29> |
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": 8356,
"vin": [ {
"gen": {
"height": 8296
}
}
],
"vout": [ {
"amount": 34632084056635,
"target": {
"tagged_key": {
"key": "0377dcf206d17c816398ea9b6973cfc888aa0284522cca525f59a24783fe005a",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 84, 18, 27, 211, 253, 231, 247, 84, 126, 129, 40, 177, 182, 27, 9, 151, 37, 29, 46, 223, 163, 249, 155, 132, 218, 193, 226, 7, 140, 241, 63, 102, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}