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: 4dc5bee81987408166629106f6ebfe73d47a5c2e51572051bf43f59e4ebf2f03
Tx prefix hash: 52a62c23fb1a0211121ca7d331f42976de5df1ba8a44b74f2f3a3210a2ac729d
Tx public key: e41519c1ea4ecbb56ee8efd0833242694c4ec09f1dba095557e99b21e21ac1c0
| Timestamp: 1780857690 | Timestamp [UTC]: 2026-06-07 18:41:30 | Age [y:d:h:m:s]: 00:001:02:30:37 |
| Block: 7587 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 299 | RingCT/type: yes/0 |
| Extra: 01e41519c1ea4ecbb56ee8efd0833242694c4ec09f1dba095557e99b21e21ac1c0020900000002e49593ff00 | ||
1 output(s) for total of 34.685567102073 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9e17c71911bf21df93a2a21001b85c0e9cac9352ae0d3ec8ff69d90425a8a23e | 34.685567102073 | 9371 of 0 | <35> |
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": 7647,
"vin": [ {
"gen": {
"height": 7587
}
}
],
"vout": [ {
"amount": 34685567102073,
"target": {
"tagged_key": {
"key": "9e17c71911bf21df93a2a21001b85c0e9cac9352ae0d3ec8ff69d90425a8a23e",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 228, 21, 25, 193, 234, 78, 203, 181, 110, 232, 239, 208, 131, 50, 66, 105, 76, 78, 192, 159, 29, 186, 9, 85, 87, 233, 155, 33, 226, 26, 193, 192, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}