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: 824a0d3d32efd8e97408431f1f5dbe59705e19ce70674a44e78307c326d5a5f3
Tx prefix hash: 8c6ce564950c4a4ece606881d7ebe62fd56bbf6a89dc5996ef67ad4ce6762bac
Tx public key: 9a725b059d950ee287d4317986b38f38084aa88eddcc766a66540c2e4df360db
| Timestamp: 1780387234 | Timestamp [UTC]: 2026-06-02 08:00:34 | Age [y:d:h:m:s]: 00:006:17:35:23 |
| Block: 5183 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2703 | RingCT/type: yes/0 |
| Extra: 019a725b059d950ee287d4317986b38f38084aa88eddcc766a66540c2e4df360db02090000000326697be300 | ||
1 output(s) for total of 34.865768179063 HMNY
| stealth address | amount | amount idx | tag |
| 00: b0e5d3495f5e7ee2b07b9382b7feebc4f15bbee72c6ee770e3a64ea616c962d6 | 34.865768179063 | 6562 of 0 | <61> |
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": 5243,
"vin": [ {
"gen": {
"height": 5183
}
}
],
"vout": [ {
"amount": 34865768179063,
"target": {
"tagged_key": {
"key": "b0e5d3495f5e7ee2b07b9382b7feebc4f15bbee72c6ee770e3a64ea616c962d6",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 154, 114, 91, 5, 157, 149, 14, 226, 135, 212, 49, 121, 134, 179, 143, 56, 8, 74, 168, 142, 221, 204, 118, 106, 102, 84, 12, 46, 77, 243, 96, 219, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}