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: 261784805f82111c5abf066372633499adf3faa2525705a06d8a52b587f38b72
Tx prefix hash: 771a4711f2b0ff9de05cd2d3b0daf823b93aa2de9387324723b0724083c491aa
Tx public key: c8de6d3e7372f10155f29f6202ed132fd9b2876e42a9641bae0e8996c66e1cd6
| Timestamp: 1779715346 | Timestamp [UTC]: 2026-05-25 13:22:26 | Age [y:d:h:m:s]: 00:014:11:24:21 |
| Block: 1631 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6255 | RingCT/type: yes/0 |
| Extra: 01c8de6d3e7372f10155f29f6202ed132fd9b2876e42a9641bae0e8996c66e1cd6020900000004ba6d17be00 | ||
1 output(s) for total of 35.075154402147 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0f10cd46d2f88e80d762ee5c415824cbf11173c8badd3907170751dfe6725feb | 35.075154402147 | 1791 of 0 | <28> |
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": 1691,
"vin": [ {
"gen": {
"height": 1631
}
}
],
"vout": [ {
"amount": 35075154402147,
"target": {
"tagged_key": {
"key": "0f10cd46d2f88e80d762ee5c415824cbf11173c8badd3907170751dfe6725feb",
"view_tag": "28"
}
}
}
],
"extra": [ 1, 200, 222, 109, 62, 115, 114, 241, 1, 85, 242, 159, 98, 2, 237, 19, 47, 217, 178, 135, 110, 66, 169, 100, 27, 174, 14, 137, 150, 198, 110, 28, 214, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}