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: ba3a66d5f69155cf28e36ee6524ba7ba90b3100065111f2f74339936ac63ad1f
Tx prefix hash: 1fb68547746ec3dc3cd950c7ae2fbbfbc2db7817a47799f98d5535a422a583a8
Tx public key: 33b6fb7e54ba39e4c267adc28e1ccc17bd1cde04902cbb0d941ef6d98c9ae7cb
| Timestamp: 1779471079 | Timestamp [UTC]: 2026-05-22 17:31:19 | Age [y:d:h:m:s]: 00:017:08:04:38 |
| Block: 565 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7321 | RingCT/type: yes/0 |
| Extra: 0133b6fb7e54ba39e4c267adc28e1ccc17bd1cde04902cbb0d941ef6d98c9ae7cb02090000000393369e7d00 | ||
1 output(s) for total of 35.146543004438 HMNY
| stealth address | amount | amount idx | tag |
| 00: af1c6360a16071d470878a89ffd107902111774a07d45cf067a3a77c198bcec9 | 35.146543004438 | 573 of 0 | <51> |
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": 625,
"vin": [ {
"gen": {
"height": 565
}
}
],
"vout": [ {
"amount": 35146543004438,
"target": {
"tagged_key": {
"key": "af1c6360a16071d470878a89ffd107902111774a07d45cf067a3a77c198bcec9",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 51, 182, 251, 126, 84, 186, 57, 228, 194, 103, 173, 194, 142, 28, 204, 23, 189, 28, 222, 4, 144, 44, 187, 13, 148, 30, 246, 217, 140, 154, 231, 203, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}