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: 78c10890b38c6b2dc9411b7c7f227199fd6fefcb758fb4f4ce6fd2d244c37a31
Tx prefix hash: d8b4ea7820ece9e63a4a4336f8aae8fb9258bce1ef6c246a8dccdbd6bbf2195b
Tx public key: 5aa0a4f584866215bf0a0f2b3cc8e7dab726090792ef659bb25ac8887f67b913
| Timestamp: 1780903736 | Timestamp [UTC]: 2026-06-08 07:28:56 | Age [y:d:h:m:s]: 00:000:14:55:53 |
| Block: 7844 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 42 | RingCT/type: yes/0 |
| Extra: 015aa0a4f584866215bf0a0f2b3cc8e7dab726090792ef659bb25ac8887f67b9130209000000014a728a4c00 | ||
1 output(s) for total of 34.661954026140 HMNY
| stealth address | amount | amount idx | tag |
| 00: 26ec72c63269ed2e71afe255eb04ce79adb201fc482207567607f584efc78948 | 34.661954026140 | 9724 of 0 | <fe> |
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": 7904,
"vin": [ {
"gen": {
"height": 7844
}
}
],
"vout": [ {
"amount": 34661954026140,
"target": {
"tagged_key": {
"key": "26ec72c63269ed2e71afe255eb04ce79adb201fc482207567607f584efc78948",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 90, 160, 164, 245, 132, 134, 98, 21, 191, 10, 15, 43, 60, 200, 231, 218, 183, 38, 9, 7, 146, 239, 101, 155, 178, 90, 200, 136, 127, 103, 185, 19, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}