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: 5665582673096bfde71f4b388208e108bb27b221a9ad6a3b2231d683be9003c8
Tx prefix hash: b2c0afad70dc0faa2afe8eb79f3f735e0326da3c6d691f6aa5fc5ca289fff07f
Tx public key: 6de9755642a461f7115744490094b4cb61d582cfb95b45f037891576b1dfd769
| Timestamp: 1780976461 | Timestamp [UTC]: 2026-06-09 03:41:01 | Age [y:d:h:m:s]: 00:000:05:18:58 |
| Block: 7939 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 393 | RingCT/type: yes/0 |
| Extra: 016de9755642a461f7115744490094b4cb61d582cfb95b45f037891576b1dfd769020900000001e49593ff00 | ||
1 output(s) for total of 34.663117508231 HMNY
| stealth address | amount | amount idx | tag |
| 00: cd4bd856bb35d997ccb37f9c21377b8a174ff08640520ea820729d744fac2b2c | 34.663117508231 | 9845 of 0 | <c7> |
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": 7999,
"vin": [ {
"gen": {
"height": 7939
}
}
],
"vout": [ {
"amount": 34663117508231,
"target": {
"tagged_key": {
"key": "cd4bd856bb35d997ccb37f9c21377b8a174ff08640520ea820729d744fac2b2c",
"view_tag": "c7"
}
}
}
],
"extra": [ 1, 109, 233, 117, 86, 66, 164, 97, 247, 17, 87, 68, 73, 0, 148, 180, 203, 97, 213, 130, 207, 185, 91, 69, 240, 55, 137, 21, 118, 177, 223, 215, 105, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}