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: 907be59d56044b38972e3719109880bfa3bec8201546012d7e4666e8dcc013b8
Tx prefix hash: 688a87c2da5e0e7a803028bb21e07b8f03d44ebc57ce4df9bdbc752256509d3f
Tx public key: 4288b3ebe7997a7d1768ed3389e2014346f383f36355e2a7c24d962e929ddf2a
| Timestamp: 1780073340 | Timestamp [UTC]: 2026-05-29 16:49:00 | Age [y:d:h:m:s]: 00:010:08:46:57 |
| Block: 4673 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3213 | RingCT/type: yes/0 |
| Extra: 014288b3ebe7997a7d1768ed3389e2014346f383f36355e2a7c24d962e929ddf2a02090000000326697be300 | ||
1 output(s) for total of 34.906765605070 HMNY
| stealth address | amount | amount idx | tag |
| 00: 35ff7f5e99322decb5d416fc0483ec8c9b0826d467f1b407ffc2940607b18305 | 34.906765605070 | 5868 of 0 | <d5> |
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": 4733,
"vin": [ {
"gen": {
"height": 4673
}
}
],
"vout": [ {
"amount": 34906765605070,
"target": {
"tagged_key": {
"key": "35ff7f5e99322decb5d416fc0483ec8c9b0826d467f1b407ffc2940607b18305",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 66, 136, 179, 235, 231, 153, 122, 125, 23, 104, 237, 51, 137, 226, 1, 67, 70, 243, 131, 243, 99, 85, 226, 167, 194, 77, 150, 46, 146, 157, 223, 42, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}