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: 56c59ea45a8c9a4971118727e97fc850ac72f9209d46eba5913f8db6e92e9307
Tx prefix hash: 4c86c123d2e9551b3bb97cff01b9ec2c66419dd28404cac272f7aca8280b294b
Tx public key: f4368d808d3afd9ea02db3c324dae7fb196247fac77d738711f404182c11f24b
| Timestamp: 1780833061 | Timestamp [UTC]: 2026-06-07 11:51:01 | Age [y:d:h:m:s]: 00:001:11:27:52 |
| Block: 7367 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 519 | RingCT/type: yes/0 |
| Extra: 01f4368d808d3afd9ea02db3c324dae7fb196247fac77d738711f404182c11f24b020900000005e49593ff00 | ||
1 output(s) for total of 34.698517635642 HMNY
| stealth address | amount | amount idx | tag |
| 00: f218ddd7c2f090e899be9f616239ef1a05fc394c66d1f5e34a538dcf80044d83 | 34.698517635642 | 9069 of 0 | <af> |
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": 7427,
"vin": [ {
"gen": {
"height": 7367
}
}
],
"vout": [ {
"amount": 34698517635642,
"target": {
"tagged_key": {
"key": "f218ddd7c2f090e899be9f616239ef1a05fc394c66d1f5e34a538dcf80044d83",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 244, 54, 141, 128, 141, 58, 253, 158, 160, 45, 179, 195, 36, 218, 231, 251, 25, 98, 71, 250, 199, 125, 115, 135, 17, 244, 4, 24, 44, 17, 242, 75, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}