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: 349a6f7af004c57b49a5d809bb49c0a522f58485b85269c17887f12862df71d9
Tx prefix hash: 6ee01fccc9a33cd75f9026a9d11353fe2b4f29ba16a50b3d00957c32e3f38c95
Tx public key: cad18594a5be2b9f9c9b7d936997e8444d16b898b6c0dd39d457145d884bb353
| Timestamp: 1780838415 | Timestamp [UTC]: 2026-06-07 13:20:15 | Age [y:d:h:m:s]: 00:001:09:58:38 |
| Block: 7437 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 449 | RingCT/type: yes/0 |
| Extra: 01cad18594a5be2b9f9c9b7d936997e8444d16b898b6c0dd39d457145d884bb353020900000001e49593ff00 | ||
1 output(s) for total of 34.697100657911 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6d785f9cc1b7bc6c192e878a60c78802dad11a8984909b6e55feacadac5452b9 | 34.697100657911 | 9157 of 0 | <30> |
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": 7497,
"vin": [ {
"gen": {
"height": 7437
}
}
],
"vout": [ {
"amount": 34697100657911,
"target": {
"tagged_key": {
"key": "6d785f9cc1b7bc6c192e878a60c78802dad11a8984909b6e55feacadac5452b9",
"view_tag": "30"
}
}
}
],
"extra": [ 1, 202, 209, 133, 148, 165, 190, 43, 159, 156, 155, 125, 147, 105, 151, 232, 68, 77, 22, 184, 152, 182, 192, 221, 57, 212, 87, 20, 93, 136, 75, 179, 83, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}