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: 7954741d85c5b3cab841aaed2f34d9f8d1c488037130504611b691f1c932d806
Tx prefix hash: b2127c006c257f0d7338e553635131ae1ef0623c2528ad17da5bd1ef5d99591c
Tx public key: 60229fd3ba2145b663c9120952fd884851bdc5f8d92b41a2463cb5e42922b37d
| Timestamp: 1779707751 | Timestamp [UTC]: 2026-05-25 11:15:51 | Age [y:d:h:m:s]: 00:014:12:03:02 |
| Block: 1567 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6319 | RingCT/type: yes/0 |
| Extra: 0160229fd3ba2145b663c9120952fd884851bdc5f8d92b41a2463cb5e42922b37d020900000003ba6d17be00 | ||
1 output(s) for total of 35.079436302630 HMNY
| stealth address | amount | amount idx | tag |
| 00: dbcfad7b02b78d4a526ee3662c238de2775f4fd2a945089bd2b8bbf13611f89b | 35.079436302630 | 1725 of 0 | <26> |
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": 1627,
"vin": [ {
"gen": {
"height": 1567
}
}
],
"vout": [ {
"amount": 35079436302630,
"target": {
"tagged_key": {
"key": "dbcfad7b02b78d4a526ee3662c238de2775f4fd2a945089bd2b8bbf13611f89b",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 96, 34, 159, 211, 186, 33, 69, 182, 99, 201, 18, 9, 82, 253, 136, 72, 81, 189, 197, 248, 217, 43, 65, 162, 70, 60, 181, 228, 41, 34, 179, 125, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}