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: f52835c3ff2a7d87827f2ab5caa9e3d987c43377f29c67d860782c5dfdd2d68a
Tx prefix hash: 659e2656db0d1a2f775d8d71957a3f11a1c828f2809aebda657e7ddeaf0bfee6
Tx public key: 0946ae561b6f3b21088c79c89a3b2396e5c459998a828d99a5a95b1515a87da6
| Timestamp: 1780984965 | Timestamp [UTC]: 2026-06-09 06:02:45 | Age [y:d:h:m:s]: 00:000:08:46:10 |
| Block: 8126 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 513 | RingCT/type: yes/0 |
| Extra: 010946ae561b6f3b21088c79c89a3b2396e5c459998a828d99a5a95b1515a87da6020900000002e49593ff00 | ||
1 output(s) for total of 34.643315316001 HMNY
| stealth address | amount | amount idx | tag |
| 00: d1e3f01e9f788544b712196cdf3b05167948d539e84851b8dda4f53f4d924df0 | 34.643315316001 | 10064 of 0 | <15> |
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": 8186,
"vin": [ {
"gen": {
"height": 8126
}
}
],
"vout": [ {
"amount": 34643315316001,
"target": {
"tagged_key": {
"key": "d1e3f01e9f788544b712196cdf3b05167948d539e84851b8dda4f53f4d924df0",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 9, 70, 174, 86, 27, 111, 59, 33, 8, 140, 121, 200, 154, 59, 35, 150, 229, 196, 89, 153, 138, 130, 141, 153, 165, 169, 91, 21, 21, 168, 125, 166, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}