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: a8cc3153e36d8a17eb2c1fcf0f177612f9ee32fd483b36119ff94075475374e4
Tx prefix hash: a5836d474030c8f4741abc7ef1c163f5c449c897c5b05b695778e1b14a90b868
Tx public key: ef077892abc5e297a4ebe7f0c92c537241f80640d869fa7541d8c39697b88188
| Timestamp: 1781019129 | Timestamp [UTC]: 2026-06-09 15:32:09 | Age [y:d:h:m:s]: 00:006:04:54:49 |
| Block: 8670 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 75 | RingCT/type: yes/0 |
| Extra: 01ef077892abc5e297a4ebe7f0c92c537241f80640d869fa7541d8c39697b88188020900000004e49593ff00 | ||
1 output(s) for total of 34.607388101182 HMNY
| stealth address | amount | amount idx | tag |
| 00: f19f31a1d0577fae3f7c2774bd2e6965938b4c04eef454e5e39219c06a664308 | 34.607388101182 | 10720 of 0 | <c5> |
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": 8730,
"vin": [ {
"gen": {
"height": 8670
}
}
],
"vout": [ {
"amount": 34607388101182,
"target": {
"tagged_key": {
"key": "f19f31a1d0577fae3f7c2774bd2e6965938b4c04eef454e5e39219c06a664308",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 239, 7, 120, 146, 171, 197, 226, 151, 164, 235, 231, 240, 201, 44, 83, 114, 65, 248, 6, 64, 216, 105, 250, 117, 65, 216, 195, 150, 151, 184, 129, 136, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}