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: aaae8d2cba05dfa967ec79cec559b557b7e3445108f44272b7d9649706d42e5d
Tx prefix hash: 38d5c7ce55174bce809297719a9cc590854a986c77f6ce8501226501b069de34
Tx public key: ffa2706e631b8ccefa326424e147c21341caaa9f4cc2aff7bafb0e439f4976e5
| Timestamp: 1779876534 | Timestamp [UTC]: 2026-05-27 10:08:54 | Age [y:d:h:m:s]: 00:017:00:53:22 |
| Block: 2893 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5852 | RingCT/type: yes/0 |
| Extra: 01ffa2706e631b8ccefa326424e147c21341caaa9f4cc2aff7bafb0e439f4976e502090000000126697be300 | ||
1 output(s) for total of 34.999822561838 HMNY
| stealth address | amount | amount idx | tag |
| 00: 857ab85e6f970b5c9c19800f5e294c2f133695df2752dc25a56e24c4b85fbb1a | 34.999822561838 | 3425 of 0 | <1f> |
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": 2953,
"vin": [ {
"gen": {
"height": 2893
}
}
],
"vout": [ {
"amount": 34999822561838,
"target": {
"tagged_key": {
"key": "857ab85e6f970b5c9c19800f5e294c2f133695df2752dc25a56e24c4b85fbb1a",
"view_tag": "1f"
}
}
}
],
"extra": [ 1, 255, 162, 112, 110, 99, 27, 140, 206, 250, 50, 100, 36, 225, 71, 194, 19, 65, 202, 170, 159, 76, 194, 175, 247, 186, 251, 14, 67, 159, 73, 118, 229, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}