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: c59fc27cc78e46261acb617eb0e27bbca04858a0ce8104d697dbbc9b393511b2
Tx prefix hash: ffd7a7421ae3357a991ad79bc1e77b14a16a4a1845b392123206ffb2b075ab04
Tx public key: f275f48e634e7a474d95a8030eec73156393deaa20d2106286aa707aed5ac5b5
| Timestamp: 1780771301 | Timestamp [UTC]: 2026-06-06 18:41:41 | Age [y:d:h:m:s]: 00:002:04:37:12 |
| Block: 6666 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1220 | RingCT/type: yes/0 |
| Extra: 01f275f48e634e7a474d95a8030eec73156393deaa20d2106286aa707aed5ac5b5020900000001e49593ff00 | ||
1 output(s) for total of 34.745750502515 HMNY
| stealth address | amount | amount idx | tag |
| 00: a90c60f08b69fb8e88fb6e6b7261d5857588bbaf7514c72e7cedf311b708b8cd | 34.745750502515 | 8220 of 0 | <a6> |
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": 6726,
"vin": [ {
"gen": {
"height": 6666
}
}
],
"vout": [ {
"amount": 34745750502515,
"target": {
"tagged_key": {
"key": "a90c60f08b69fb8e88fb6e6b7261d5857588bbaf7514c72e7cedf311b708b8cd",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 242, 117, 244, 142, 99, 78, 122, 71, 77, 149, 168, 3, 14, 236, 115, 21, 99, 147, 222, 170, 32, 210, 16, 98, 134, 170, 112, 122, 237, 90, 197, 181, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}