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: d86e3144e53777af61b48d5416e15eae81d948147fccf8b779af8c588249d504
Tx prefix hash: f74479fcff1f6c130b039610b5ba0bb6923223e27b1a9046ce9c51355579a893
Tx public key: d5c0914eea3c2850e168085bdcaeaf0ba716cc110f1883e197d0c65dc1020c2e
| Timestamp: 1780694202 | Timestamp [UTC]: 2026-06-05 21:16:42 | Age [y:d:h:m:s]: 00:003:04:19:15 |
| Block: 5922 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1964 | RingCT/type: yes/0 |
| Extra: 01d5c0914eea3c2850e168085bdcaeaf0ba716cc110f1883e197d0c65dc1020c2e020900000001e49593ff00 | ||
1 output(s) for total of 34.789255435283 HMNY
| stealth address | amount | amount idx | tag |
| 00: 82786d591f09d83e85392a86f432ea619b12640a4cb0341376a7226672c6f57e | 34.789255435283 | 7383 of 0 | <07> |
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": 5982,
"vin": [ {
"gen": {
"height": 5922
}
}
],
"vout": [ {
"amount": 34789255435283,
"target": {
"tagged_key": {
"key": "82786d591f09d83e85392a86f432ea619b12640a4cb0341376a7226672c6f57e",
"view_tag": "07"
}
}
}
],
"extra": [ 1, 213, 192, 145, 78, 234, 60, 40, 80, 225, 104, 8, 91, 220, 174, 175, 11, 167, 22, 204, 17, 15, 24, 131, 225, 151, 208, 198, 93, 193, 2, 12, 46, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}