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: 1bb3722ace5525efadd0bc3fa7ea19b5cafdf07111b961bd9f7ad20a93c24326
Tx prefix hash: d72acbccaeb49180e98343f90959bd3b2b0b6851a1d95bb7708ab9140c95cb5b
Tx public key: 864ff75bfa6a831fa45b220b6726d81f56cd5e30c1b5c3730902840f6aab6817
| Timestamp: 1779442887 | Timestamp [UTC]: 2026-05-22 09:41:27 | Age [y:d:h:m:s]: 00:017:15:05:20 |
| Block: 228 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7658 | RingCT/type: yes/0 |
| Extra: 01864ff75bfa6a831fa45b220b6726d81f56cd5e30c1b5c3730902840f6aab68170209000000024438f87f00 | ||
1 output(s) for total of 35.169141659676 HMNY
| stealth address | amount | amount idx | tag |
| 00: 37aeb173b9362e6864c11bcc0531d56bbbba4e424764f9fdaf0d970ecb9b1c05 | 35.169141659676 | 224 of 0 | <11> |
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": 288,
"vin": [ {
"gen": {
"height": 228
}
}
],
"vout": [ {
"amount": 35169141659676,
"target": {
"tagged_key": {
"key": "37aeb173b9362e6864c11bcc0531d56bbbba4e424764f9fdaf0d970ecb9b1c05",
"view_tag": "11"
}
}
}
],
"extra": [ 1, 134, 79, 247, 91, 250, 106, 131, 31, 164, 91, 34, 11, 103, 38, 216, 31, 86, 205, 94, 48, 193, 181, 195, 115, 9, 2, 132, 15, 106, 171, 104, 23, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}