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: ff9df74e3ae75bac233e9f723d254b69e9646b51a1a30c9ed6e603f4b46cd8cd
Tx prefix hash: e4a68bf7e10e3f17476133864663b5345064eb02b18494abdea5a7cd208f6faf
Tx public key: 29b39dc72f1c12bdbe2ea84db3a95ba28aa8d2aa393506ee3a968e86a1840a46
| Timestamp: 1780074083 | Timestamp [UTC]: 2026-05-29 17:01:23 | Age [y:d:h:m:s]: 00:010:07:45:24 |
| Block: 4679 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3207 | RingCT/type: yes/0 |
| Extra: 0129b39dc72f1c12bdbe2ea84db3a95ba28aa8d2aa393506ee3a968e86a1840a4602090000000126697be300 | ||
1 output(s) for total of 34.876052125948 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e5e2fffdb0ca07325629d62e2e844111e53a3f340e51ea82c09639f84080e1e | 34.876052125948 | 5877 of 0 | <96> |
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": 4739,
"vin": [ {
"gen": {
"height": 4679
}
}
],
"vout": [ {
"amount": 34876052125948,
"target": {
"tagged_key": {
"key": "3e5e2fffdb0ca07325629d62e2e844111e53a3f340e51ea82c09639f84080e1e",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 41, 179, 157, 199, 47, 28, 18, 189, 190, 46, 168, 77, 179, 169, 91, 162, 138, 168, 210, 170, 57, 53, 6, 238, 58, 150, 142, 134, 161, 132, 10, 70, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}