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: d9f4176056176e1169d0d9c8eb5a2f5395e24c92a498a5f6fe3c4c5162218fe1
Tx prefix hash: 96af5768c7c82445b59f704c8c336240651b45024aaba35037f80198dbd68a98
Tx public key: b045854381f372c2bc01aadd53d565ccee802fed960ee9ad5f9ddc5ff03f2546
| Timestamp: 1779859727 | Timestamp [UTC]: 2026-05-27 05:28:47 | Age [y:d:h:m:s]: 00:012:22:22:11 |
| Block: 2666 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5299 | RingCT/type: yes/0 |
| Extra: 01b045854381f372c2bc01aadd53d565ccee802fed960ee9ad5f9ddc5ff03f254602090000000326697be300 | ||
1 output(s) for total of 35.014177769908 HMNY
| stealth address | amount | amount idx | tag |
| 00: f41f1e1b0855c607db3995cb7546e3acf28d8f1c4b2848297b6d9e5d10fd2419 | 35.014177769908 | 3142 of 0 | <16> |
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": 2726,
"vin": [ {
"gen": {
"height": 2666
}
}
],
"vout": [ {
"amount": 35014177769908,
"target": {
"tagged_key": {
"key": "f41f1e1b0855c607db3995cb7546e3acf28d8f1c4b2848297b6d9e5d10fd2419",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 176, 69, 133, 67, 129, 243, 114, 194, 188, 1, 170, 221, 83, 213, 101, 204, 238, 128, 47, 237, 150, 14, 233, 173, 95, 157, 220, 95, 240, 63, 37, 70, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}