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: 8c293edd652ed4040efca6025682757ad6f27897df9c25518042d37414efd75b
Tx prefix hash: a5c1bafe1cccc48b6da6234e347b37e492d8cf168136634d2b2251b885e09451
Tx public key: 444aef3ff813b80b63d0872e19e5980245bc0bc4da653a6cffdd1cd7c5c42584
| Timestamp: 1779853933 | Timestamp [UTC]: 2026-05-27 03:52:13 | Age [y:d:h:m:s]: 00:012:22:57:35 |
| Block: 2581 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5317 | RingCT/type: yes/0 |
| Extra: 01444aef3ff813b80b63d0872e19e5980245bc0bc4da653a6cffdd1cd7c5c4258402090000000126697be300 | ||
1 output(s) for total of 35.011656367182 HMNY
| stealth address | amount | amount idx | tag |
| 00: 76cccaf65bd5a4d6696f5e5f7059a0ff4d31e920d927d25617c015dfa94708e3 | 35.011656367182 | 3039 of 0 | <53> |
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": 2641,
"vin": [ {
"gen": {
"height": 2581
}
}
],
"vout": [ {
"amount": 35011656367182,
"target": {
"tagged_key": {
"key": "76cccaf65bd5a4d6696f5e5f7059a0ff4d31e920d927d25617c015dfa94708e3",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 68, 74, 239, 63, 248, 19, 184, 11, 99, 208, 135, 46, 25, 229, 152, 2, 69, 188, 11, 196, 218, 101, 58, 108, 255, 221, 28, 215, 197, 196, 37, 132, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}