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: 83267d4ef73c4b6b296b23f178e3268c87001de3ca8c81bd9b49c057dc53caf7
Tx prefix hash: 716aad00a5f0055575a9a520efcfd838eef66eafb952381656c7d176db91a401
Tx public key: f6275bc9f8bd421087755d172f6a3dacb0a84cd9806833aeeefe6825e2726124
| Timestamp: 1779456640 | Timestamp [UTC]: 2026-05-22 13:30:40 | Age [y:d:h:m:s]: 00:017:12:05:17 |
| Block: 393 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7493 | RingCT/type: yes/0 |
| Extra: 01f6275bc9f8bd421087755d172f6a3dacb0a84cd9806833aeeefe6825e272612402090000000293369e7d00 | ||
1 output(s) for total of 35.158075221233 HMNY
| stealth address | amount | amount idx | tag |
| 00: df01fae492e1b170daea82ea242ed031763347898164c3bd36dfffb9d51fbf2d | 35.158075221233 | 393 of 0 | <df> |
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": 453,
"vin": [ {
"gen": {
"height": 393
}
}
],
"vout": [ {
"amount": 35158075221233,
"target": {
"tagged_key": {
"key": "df01fae492e1b170daea82ea242ed031763347898164c3bd36dfffb9d51fbf2d",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 246, 39, 91, 201, 248, 189, 66, 16, 135, 117, 93, 23, 47, 106, 61, 172, 176, 168, 76, 217, 128, 104, 51, 174, 238, 254, 104, 37, 226, 114, 97, 36, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}