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: 8a3da461904207d4edd3c885f040fa190c32e677e363fb219d376258d90133bd
Tx prefix hash: baa67dab82835ca9a0a136d823b18bf67cdf904db9bef6f097d834fb6c29f0e8
Tx public key: 79c199a098bfe101fa5b936bf0d387f7326c28523ee84e2a08a1b618e8d5d1d8
| Timestamp: 1779785994 | Timestamp [UTC]: 2026-05-26 08:59:54 | Age [y:d:h:m:s]: 00:021:23:36:20 |
| Block: 2164 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6581 | RingCT/type: yes/0 |
| Extra: 0179c199a098bfe101fa5b936bf0d387f7326c28523ee84e2a08a1b618e8d5d1d802090000000226697be300 | ||
1 output(s) for total of 35.039514495317 HMNY
| stealth address | amount | amount idx | tag |
| 00: e7f6ea150d4eb6f35030dbcd86adb9853b25ff785501f9c5f6ad9dfb71c9e24e | 35.039514495317 | 2500 of 0 | <8c> |
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": 2224,
"vin": [ {
"gen": {
"height": 2164
}
}
],
"vout": [ {
"amount": 35039514495317,
"target": {
"tagged_key": {
"key": "e7f6ea150d4eb6f35030dbcd86adb9853b25ff785501f9c5f6ad9dfb71c9e24e",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 121, 193, 153, 160, 152, 191, 225, 1, 250, 91, 147, 107, 240, 211, 135, 247, 50, 108, 40, 82, 62, 232, 78, 42, 8, 161, 182, 24, 232, 213, 209, 216, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}