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: 755eaf72ddab6b90eabd6fa01ef6df92806f2e15110211bd474562d0c86a53a3
Tx prefix hash: 3ff489fa5da42ada3fcb97ff37c458a1fc4dde15de0d8c72827481c7f2651068
Tx public key: 12d5a304bc668caf54f77469dd0b0110dbb4a85b9d781bd43c9a6fc53a5c3546
| Timestamp: 1780981091 | Timestamp [UTC]: 2026-06-09 04:58:11 | Age [y:d:h:m:s]: 00:000:08:39:25 |
| Block: 8032 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 569 | RingCT/type: yes/0 |
| Extra: 0112d5a304bc668caf54f77469dd0b0110dbb4a85b9d781bd43c9a6fc53a5c3546020900000003e49593ff00 | ||
1 output(s) for total of 34.649527105497 HMNY
| stealth address | amount | amount idx | tag |
| 00: ac06628187c3bcf5e34816889c58db501b0378e10a68594dda002d5ee0870ba7 | 34.649527105497 | 9956 of 0 | <05> |
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": 8092,
"vin": [ {
"gen": {
"height": 8032
}
}
],
"vout": [ {
"amount": 34649527105497,
"target": {
"tagged_key": {
"key": "ac06628187c3bcf5e34816889c58db501b0378e10a68594dda002d5ee0870ba7",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 18, 213, 163, 4, 188, 102, 140, 175, 84, 247, 116, 105, 221, 11, 1, 16, 219, 180, 168, 91, 157, 120, 27, 212, 60, 154, 111, 197, 58, 92, 53, 70, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}