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: 0fa43f44f3169671a43cb6768f70b5fb749f7ad706dd3d0f3c1123c4658c67bc
Tx prefix hash: bc785d59e584ca25771087b7a3dc1e2e2d5edeb3ee3d37f68fc36d2eba2007dd
Tx public key: 822686f9d7e019260db8aa107a8fee848d649e5c83b64ee2de9ccda82b7e101f
| Timestamp: 1779733256 | Timestamp [UTC]: 2026-05-25 18:20:56 | Age [y:d:h:m:s]: 00:014:07:15:01 |
| Block: 1897 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5989 | RingCT/type: yes/0 |
| Extra: 01822686f9d7e019260db8aa107a8fee848d649e5c83b64ee2de9ccda82b7e101f020900000001ba6d17be00 | ||
1 output(s) for total of 35.085371353035 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8666bd7f6a78e5571636d3aab0ec29e95c1376583789a8e6c86d8af4b0241d02 | 35.085371353035 | 2120 of 0 | <19> |
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": 1957,
"vin": [ {
"gen": {
"height": 1897
}
}
],
"vout": [ {
"amount": 35085371353035,
"target": {
"tagged_key": {
"key": "8666bd7f6a78e5571636d3aab0ec29e95c1376583789a8e6c86d8af4b0241d02",
"view_tag": "19"
}
}
}
],
"extra": [ 1, 130, 38, 134, 249, 215, 224, 25, 38, 13, 184, 170, 16, 122, 143, 238, 132, 141, 100, 158, 92, 131, 182, 78, 226, 222, 156, 205, 168, 43, 126, 16, 31, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}