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: fe8917cb7389421e31ab0bde7ee62ed6724d6a73c024a71105e7a7ae84b232fd
Tx prefix hash: 7db4c1659e642f6e11e1cd3ea25b2c7a315200c2551978696fba768f478630c5
Tx public key: 811771142e5ba7f90e49eb37d91b9517fe3684f055ead0f802ae73fd221f4126
| Timestamp: 1779452188 | Timestamp [UTC]: 2026-05-22 12:16:28 | Age [y:d:h:m:s]: 00:017:13:19:29 |
| Block: 345 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7541 | RingCT/type: yes/0 |
| Extra: 01811771142e5ba7f90e49eb37d91b9517fe3684f055ead0f802ae73fd221f41260209000000034438f87f00 | ||
1 output(s) for total of 35.161294189575 HMNY
| stealth address | amount | amount idx | tag |
| 00: ad0eca987151a2506a4fc9792565505c3bfaa7965a2acd684dd81eda6c3c9c6e | 35.161294189575 | 341 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": 405,
"vin": [ {
"gen": {
"height": 345
}
}
],
"vout": [ {
"amount": 35161294189575,
"target": {
"tagged_key": {
"key": "ad0eca987151a2506a4fc9792565505c3bfaa7965a2acd684dd81eda6c3c9c6e",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 129, 23, 113, 20, 46, 91, 167, 249, 14, 73, 235, 55, 217, 27, 149, 23, 254, 54, 132, 240, 85, 234, 208, 248, 2, 174, 115, 253, 34, 31, 65, 38, 2, 9, 0, 0, 0, 3, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}