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: 8414b204fe43bff4e2cde99f0601a4c9c95479025bcadd282ad3f3f7923752a7
Tx prefix hash: 1eddcbbbd050867a0e295ddc2cc40d4688334f934388f2e221fc436ea62e632b
Tx public key: 6a7882f51449974310843b8e894b12b2c3642d97abab60b42ca4ff8671087583
| Timestamp: 1779448533 | Timestamp [UTC]: 2026-05-22 11:15:33 | Age [y:d:h:m:s]: 00:017:14:20:24 |
| Block: 303 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7583 | RingCT/type: yes/0 |
| Extra: 016a7882f51449974310843b8e894b12b2c3642d97abab60b42ca4ff86710875830209000000034438f87f00 | ||
1 output(s) for total of 35.164111028636 HMNY
| stealth address | amount | amount idx | tag |
| 00: 069a3718f5e3a73b6c88714bb60c8dfda5fce9aac5b10d8f2639e8a45bdf6cfb | 35.164111028636 | 299 of 0 | <26> |
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": 363,
"vin": [ {
"gen": {
"height": 303
}
}
],
"vout": [ {
"amount": 35164111028636,
"target": {
"tagged_key": {
"key": "069a3718f5e3a73b6c88714bb60c8dfda5fce9aac5b10d8f2639e8a45bdf6cfb",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 106, 120, 130, 245, 20, 73, 151, 67, 16, 132, 59, 142, 137, 75, 18, 178, 195, 100, 45, 151, 171, 171, 96, 180, 44, 164, 255, 134, 113, 8, 117, 131, 2, 9, 0, 0, 0, 3, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}