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: 22329cd4fbd0bb9b30b2e5adb7c21ef3e13fe95c221eec469639860e6d6c5ebd
Tx prefix hash: 9c9d5e98a91bfd85edf85418c6233c6f1aed71fa4bcaedb68461db5a8e86d8fa
Tx public key: e4a68fef237e6318253bcd5fb27ee4d2440a186a898f093e9b61acbf7afba1d8
| Timestamp: 1779968202 | Timestamp [UTC]: 2026-05-28 11:36:42 | Age [y:d:h:m:s]: 00:011:13:10:05 |
| Block: 3824 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4062 | RingCT/type: yes/0 |
| Extra: 01e4a68fef237e6318253bcd5fb27ee4d2440a186a898f093e9b61acbf7afba1d802090000000726697be300 | ||
1 output(s) for total of 34.934466970637 HMNY
| stealth address | amount | amount idx | tag |
| 00: c6bbff87e944efda7a51f7fea35718bb054174e2e393c675142ce88173a6993e | 34.934466970637 | 4656 of 0 | <4d> |
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": 3884,
"vin": [ {
"gen": {
"height": 3824
}
}
],
"vout": [ {
"amount": 34934466970637,
"target": {
"tagged_key": {
"key": "c6bbff87e944efda7a51f7fea35718bb054174e2e393c675142ce88173a6993e",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 228, 166, 143, 239, 35, 126, 99, 24, 37, 59, 205, 95, 178, 126, 228, 210, 68, 10, 24, 106, 137, 143, 9, 62, 155, 97, 172, 191, 122, 251, 161, 216, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}