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: f9d1abcaf31ed213be05882011f6e445a3bcfba844ac8e3533687942174112b9
Tx prefix hash: 9a33844cd98a46f8f726983faf30a6609766b162cc64bc920c719dc749d90943
Tx public key: 603f33b081d38e82627da6d7944e33cec09a0005457ed966d354a693991258a9
| Timestamp: 1779456326 | Timestamp [UTC]: 2026-05-22 13:25:26 | Age [y:d:h:m:s]: 00:017:13:15:10 |
| Block: 387 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7510 | RingCT/type: yes/0 |
| Extra: 01603f33b081d38e82627da6d7944e33cec09a0005457ed966d354a693991258a902090000000193369e7d00 | ||
1 output(s) for total of 35.158477576160 HMNY
| stealth address | amount | amount idx | tag |
| 00: c28d695619fa5982781c849f8483c7d2f3b183d7e174004ac8e2e6b0233e9186 | 35.158477576160 | 387 of 0 | <70> |
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": 447,
"vin": [ {
"gen": {
"height": 387
}
}
],
"vout": [ {
"amount": 35158477576160,
"target": {
"tagged_key": {
"key": "c28d695619fa5982781c849f8483c7d2f3b183d7e174004ac8e2e6b0233e9186",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 96, 63, 51, 176, 129, 211, 142, 130, 98, 125, 166, 215, 148, 78, 51, 206, 192, 154, 0, 5, 69, 126, 217, 102, 211, 84, 166, 147, 153, 18, 88, 169, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}