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: 9c7a8b87bc9c196b41f26758fd55232e17cfad1e8004e51407747e31a5575d52
Tx prefix hash: 1bca3db030966dffaa980fab46615ebd4a921d64a34c0fa14be8b665f8b1cbd9
Tx public key: fcec5b139013d78c585489d8ac45fec0ede19d69548364c0f779cbc934c5cde6
| Timestamp: 1779636410 | Timestamp [UTC]: 2026-05-24 15:26:50 | Age [y:d:h:m:s]: 00:015:10:09:07 |
| Block: 1114 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6772 | RingCT/type: yes/0 |
| Extra: 01fcec5b139013d78c585489d8ac45fec0ede19d69548364c0f779cbc934c5cde6020900000001ba6d17be00 | ||
1 output(s) for total of 35.109759077376 HMNY
| stealth address | amount | amount idx | tag |
| 00: b7b0a9621873246cf6436a2afd87b684953fdce86e470b2b515b897cf7b0b8d8 | 35.109759077376 | 1254 of 0 | <3e> |
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": 1174,
"vin": [ {
"gen": {
"height": 1114
}
}
],
"vout": [ {
"amount": 35109759077376,
"target": {
"tagged_key": {
"key": "b7b0a9621873246cf6436a2afd87b684953fdce86e470b2b515b897cf7b0b8d8",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 252, 236, 91, 19, 144, 19, 215, 140, 88, 84, 137, 216, 172, 69, 254, 192, 237, 225, 157, 105, 84, 131, 100, 192, 247, 121, 203, 201, 52, 197, 205, 230, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}