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: fe569e676c8309e3e4812d813ed2ae2438d30891b5845e26bf1011de230bc8ac
Tx prefix hash: 59713485e7daa6a5237bbf706c2a9e48c2c98a8da87e33ead3cfdf4688471f46
Tx public key: caa5e9a3fb35e46f7e4766e2f31ac29565a5e98f2e60dfba2fad56b99ff027c5
| Timestamp: 1780823008 | Timestamp [UTC]: 2026-06-07 09:03:28 | Age [y:d:h:m:s]: 00:001:15:43:19 |
| Block: 7209 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 677 | RingCT/type: yes/0 |
| Extra: 01caa5e9a3fb35e46f7e4766e2f31ac29565a5e98f2e60dfba2fad56b99ff027c5020900000002e49593ff00 | ||
1 output(s) for total of 34.703960893163 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7907643b7858c502d640f7a92552c10b565d6db344579c82f14ab50441ed5669 | 34.703960893163 | 8879 of 0 | <46> |
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": 7269,
"vin": [ {
"gen": {
"height": 7209
}
}
],
"vout": [ {
"amount": 34703960893163,
"target": {
"tagged_key": {
"key": "7907643b7858c502d640f7a92552c10b565d6db344579c82f14ab50441ed5669",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 202, 165, 233, 163, 251, 53, 228, 111, 126, 71, 102, 226, 243, 26, 194, 149, 101, 165, 233, 143, 46, 96, 223, 186, 47, 173, 86, 185, 159, 240, 39, 197, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}