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: c5d770e64ef236f9f2e5e2d5dcb35730a005d30e47e937feaf11268f38c719a2
Tx prefix hash: 9f97a9e67c2c31dca3a8e6b0f43bf0ad0ccc396f5fb1ec73f8a8307d434581e0
Tx public key: ddd681cab1d164b28bba865a9a7e61a248e1c3fb2756008d4e7d59333b5bf399
| Timestamp: 1780892889 | Timestamp [UTC]: 2026-06-08 04:28:09 | Age [y:d:h:m:s]: 00:000:16:43:58 |
| Block: 7739 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 147 | RingCT/type: yes/0 |
| Extra: 01ddd681cab1d164b28bba865a9a7e61a248e1c3fb2756008d4e7d59333b5bf3990209000000034a728a4c00 | ||
1 output(s) for total of 34.668896533146 HMNY
| stealth address | amount | amount idx | tag |
| 00: 28e642bc30b36f7f59f7d0e479f7626597fc795d94b8964dbce091f947f9bf00 | 34.668896533146 | 9581 of 0 | <d0> |
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": 7799,
"vin": [ {
"gen": {
"height": 7739
}
}
],
"vout": [ {
"amount": 34668896533146,
"target": {
"tagged_key": {
"key": "28e642bc30b36f7f59f7d0e479f7626597fc795d94b8964dbce091f947f9bf00",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 221, 214, 129, 202, 177, 209, 100, 178, 139, 186, 134, 90, 154, 126, 97, 162, 72, 225, 195, 251, 39, 86, 0, 141, 78, 125, 89, 51, 59, 91, 243, 153, 2, 9, 0, 0, 0, 3, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}