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: 509b6a2c2fa8b474f45c20b3fe3903cecf82ca5e82bf80a39945861d68362f60
Tx prefix hash: 744274f1ff63cdddde95aedba2cd4fae1f11562588f513bfc3a5594c3887182a
Tx public key: db93bd4ad04b7651ed69bdf2916d76adfe1dae37fde2a622ecc96d62dad3cf8b
| Timestamp: 1779642317 | Timestamp [UTC]: 2026-05-24 17:05:17 | Age [y:d:h:m:s]: 00:015:09:35:19 |
| Block: 1383 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6514 | RingCT/type: yes/0 |
| Extra: 01db93bd4ad04b7651ed69bdf2916d76adfe1dae37fde2a622ecc96d62dad3cf8b020900000001ba6d17be00 | ||
1 output(s) for total of 35.091749678486 HMNY
| stealth address | amount | amount idx | tag |
| 00: 082502b3c643ef68c02902799220d7a1dd8c87b27a048fa68e1312d670b773db | 35.091749678486 | 1533 of 0 | <8e> |
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": 1443,
"vin": [ {
"gen": {
"height": 1383
}
}
],
"vout": [ {
"amount": 35091749678486,
"target": {
"tagged_key": {
"key": "082502b3c643ef68c02902799220d7a1dd8c87b27a048fa68e1312d670b773db",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 219, 147, 189, 74, 208, 75, 118, 81, 237, 105, 189, 242, 145, 109, 118, 173, 254, 29, 174, 55, 253, 226, 166, 34, 236, 201, 109, 98, 218, 211, 207, 139, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}