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: fe7bba40747d3bcc234a75d310f43461f6e792e4da04faac68189d8bead1d8a0
Tx prefix hash: 8f2f9fe3343566fae8cee321514671e1a2ca72af4dc1b1b066d79846650339f1
Tx public key: b20fb6d63395ff0b419d3715f61639a0ce370fcdb15fe8795b3dfd13c58e825d
| Timestamp: 1779916205 | Timestamp [UTC]: 2026-05-27 21:10:05 | Age [y:d:h:m:s]: 00:012:02:08:48 |
| Block: 3303 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4583 | RingCT/type: yes/0 |
| Extra: 01b20fb6d63395ff0b419d3715f61639a0ce370fcdb15fe8795b3dfd13c58e825d02090000000226697be300 | ||
1 output(s) for total of 34.963474752434 HMNY
| stealth address | amount | amount idx | tag |
| 00: 92b15adb90afbe2de961a627ef64114359f823c478ade5e5c5301276d585533b | 34.963474752434 | 3969 of 0 | <da> |
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": 3363,
"vin": [ {
"gen": {
"height": 3303
}
}
],
"vout": [ {
"amount": 34963474752434,
"target": {
"tagged_key": {
"key": "92b15adb90afbe2de961a627ef64114359f823c478ade5e5c5301276d585533b",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 178, 15, 182, 214, 51, 149, 255, 11, 65, 157, 55, 21, 246, 22, 57, 160, 206, 55, 15, 205, 177, 95, 232, 121, 91, 61, 253, 19, 197, 142, 130, 93, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}