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: 352e5d20325c9e444c5d90c0fb90b17a257c383ccd6df9db9329d7736a7ab4ff
Tx prefix hash: af3ba6ab818d40e30fcec203f7c723edc301e3f3fa8ed6a28109968f74ea67c1
Tx public key: 4723bff9778d0cbf6c0c6cb951cbec7b589042d65f5a27f2d908212e28d9e0a1
| Timestamp: 1779959647 | Timestamp [UTC]: 2026-05-28 09:14:07 | Age [y:d:h:m:s]: 00:011:14:04:46 |
| Block: 3738 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4148 | RingCT/type: yes/0 |
| Extra: 014723bff9778d0cbf6c0c6cb951cbec7b589042d65f5a27f2d908212e28d9e0a102090000000726697be300 | ||
1 output(s) for total of 34.934477677773 HMNY
| stealth address | amount | amount idx | tag |
| 00: ca3c4229ef56977ba303efcf021c1d2aaafbe38336403eb52d82082c75b989e5 | 34.934477677773 | 4530 of 0 | <ea> |
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": 3798,
"vin": [ {
"gen": {
"height": 3738
}
}
],
"vout": [ {
"amount": 34934477677773,
"target": {
"tagged_key": {
"key": "ca3c4229ef56977ba303efcf021c1d2aaafbe38336403eb52d82082c75b989e5",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 71, 35, 191, 249, 119, 141, 12, 191, 108, 12, 108, 185, 81, 203, 236, 123, 88, 144, 66, 214, 95, 90, 39, 242, 217, 8, 33, 46, 40, 217, 224, 161, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}