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: c5fa0017ad54d4fb19e6645fc7b98bf1af257dfefe70e9beb0bcf1c149c1b0dd
Tx prefix hash: 005676c495d37e78f05becbbbeb87df88848c3285ebb56e5f8390199cc2f69fa
Tx public key: 45b961dafa56402eb57f79e04e923a7166d96dbf44e74476b4118509aed61fa7
| Timestamp: 1779629597 | Timestamp [UTC]: 2026-05-24 13:33:17 | Age [y:d:h:m:s]: 00:015:14:59:45 |
| Block: 839 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7187 | RingCT/type: yes/0 |
| Extra: 0145b961dafa56402eb57f79e04e923a7166d96dbf44e74476b4118509aed61fa7020900000001ba6d17be00 | ||
1 output(s) for total of 35.128179727047 HMNY
| stealth address | amount | amount idx | tag |
| 00: 581be2eed3b3511c79dfc93dbb3500f2b7cf494e9b5c161f6acdc834f85c5d1a | 35.128179727047 | 971 of 0 | <39> |
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": 899,
"vin": [ {
"gen": {
"height": 839
}
}
],
"vout": [ {
"amount": 35128179727047,
"target": {
"tagged_key": {
"key": "581be2eed3b3511c79dfc93dbb3500f2b7cf494e9b5c161f6acdc834f85c5d1a",
"view_tag": "39"
}
}
}
],
"extra": [ 1, 69, 185, 97, 218, 250, 86, 64, 46, 181, 127, 121, 224, 78, 146, 58, 113, 102, 217, 109, 191, 68, 231, 68, 118, 180, 17, 133, 9, 174, 214, 31, 167, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}