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: 886017f476d0df46794e8d566eaba6181ec1562f9ea6de4845b40596ee5bd6b2
Tx prefix hash: 9b50c52a112b4694c7a0b738f0b9cf5c45b160016b0154cec716afd527e0978a
Tx public key: fe323f703702baf62bb0bb3504cd23e310c950b40164e053f438a959d7434ffc
| Timestamp: 1779726574 | Timestamp [UTC]: 2026-05-25 16:29:34 | Age [y:d:h:m:s]: 00:014:04:42:33 |
| Block: 1861 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6025 | RingCT/type: yes/0 |
| Extra: 01fe323f703702baf62bb0bb3504cd23e310c950b40164e053f438a959d7434ffc020900000004ba6d17be00 | ||
1 output(s) for total of 35.062378236083 HMNY
| stealth address | amount | amount idx | tag |
| 00: 91932ad4a8c69df92897c10c6ce180a560fc0060700f59d0d6a3a6a38e701247 | 35.062378236083 | 2062 of 0 | <ea> |
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": 1921,
"vin": [ {
"gen": {
"height": 1861
}
}
],
"vout": [ {
"amount": 35062378236083,
"target": {
"tagged_key": {
"key": "91932ad4a8c69df92897c10c6ce180a560fc0060700f59d0d6a3a6a38e701247",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 254, 50, 63, 112, 55, 2, 186, 246, 43, 176, 187, 53, 4, 205, 35, 227, 16, 201, 80, 180, 1, 100, 224, 83, 244, 56, 169, 89, 215, 67, 79, 252, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}