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: 1d6ae8520bf13b45ec660cc75f27962b4d72b589017527834a8f5bed3d20afe7
Tx prefix hash: 02c98320d2cf38fcf0ff5268571d183cb8419c13d8e8f4da2ba85594353ffbdf
Tx public key: 78f0e0c995d6a6d542504ad05259f669696ac0e2d980f510c4bd3c12537934e5
| Timestamp: 1779999337 | Timestamp [UTC]: 2026-05-28 20:15:37 | Age [y:d:h:m:s]: 00:011:03:03:16 |
| Block: 4048 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3838 | RingCT/type: yes/0 |
| Extra: 0178f0e0c995d6a6d542504ad05259f669696ac0e2d980f510c4bd3c12537934e502090000000726697be300 | ||
1 output(s) for total of 34.913827772846 HMNY
| stealth address | amount | amount idx | tag |
| 00: 03f3a9bcc02fd966c441edb8f8777d5c254d5ac9124155da018cbd62a1764893 | 34.913827772846 | 5013 of 0 | <25> |
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": 4108,
"vin": [ {
"gen": {
"height": 4048
}
}
],
"vout": [ {
"amount": 34913827772846,
"target": {
"tagged_key": {
"key": "03f3a9bcc02fd966c441edb8f8777d5c254d5ac9124155da018cbd62a1764893",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 120, 240, 224, 201, 149, 214, 166, 213, 66, 80, 74, 208, 82, 89, 246, 105, 105, 106, 192, 226, 217, 128, 245, 16, 196, 189, 60, 18, 83, 121, 52, 229, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}