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: c986f33da879789666464360f6094d7469d5090f9c8f44cf720e6a9faaa33d7a
Tx prefix hash: b454ad95b2e45b6d8f1cc7804c47616f6c2e3475b39419e26df40b98984f8087
Tx public key: 36932fd54517cb694f5a1f2636a761528ee59e23a92ecdbc1682e7fd1e3f5649
| Timestamp: 1779450882 | Timestamp [UTC]: 2026-05-22 11:54:42 | Age [y:d:h:m:s]: 00:017:13:41:15 |
| Block: 325 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7561 | RingCT/type: yes/0 |
| Extra: 0136932fd54517cb694f5a1f2636a761528ee59e23a92ecdbc1682e7fd1e3f56490209000000064438f87f00 | ||
1 output(s) for total of 35.162635513366 HMNY
| stealth address | amount | amount idx | tag |
| 00: e229123555e5f0347a8e374cd2e26fc87ba1e3e6ed4b7d67b03d0d93c6f4e661 | 35.162635513366 | 321 of 0 | <61> |
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": 385,
"vin": [ {
"gen": {
"height": 325
}
}
],
"vout": [ {
"amount": 35162635513366,
"target": {
"tagged_key": {
"key": "e229123555e5f0347a8e374cd2e26fc87ba1e3e6ed4b7d67b03d0d93c6f4e661",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 54, 147, 47, 213, 69, 23, 203, 105, 79, 90, 31, 38, 54, 167, 97, 82, 142, 229, 158, 35, 169, 46, 205, 188, 22, 130, 231, 253, 30, 63, 86, 73, 2, 9, 0, 0, 0, 6, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}