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: 5c9105932079e56cc1394f28a89d37d330dd567dbb89ec1196f59b5ba63ee069
Tx prefix hash: d1a0044809d14913dd646430e3eb93d5ea88dfe90c64a9b3a1d709099899047f
Tx public key: 4e4f91ceed6465f68d6a3fc3d28bde14b9131661ddd80e14756a720fac979b56
| Timestamp: 1780980189 | Timestamp [UTC]: 2026-06-09 04:43:09 | Age [y:d:h:m:s]: 00:000:04:16:50 |
| Block: 8015 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 317 | RingCT/type: yes/0 |
| Extra: 014e4f91ceed6465f68d6a3fc3d28bde14b9131661ddd80e14756a720fac979b56020900000002e49593ff00 | ||
1 output(s) for total of 34.650650633162 HMNY
| stealth address | amount | amount idx | tag |
| 00: 618045bc7501a7f758842cfe7448446c75a7636671f7c91c601fc7f098255ec1 | 34.650650633162 | 9937 of 0 | <af> |
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": 8075,
"vin": [ {
"gen": {
"height": 8015
}
}
],
"vout": [ {
"amount": 34650650633162,
"target": {
"tagged_key": {
"key": "618045bc7501a7f758842cfe7448446c75a7636671f7c91c601fc7f098255ec1",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 78, 79, 145, 206, 237, 100, 101, 246, 141, 106, 63, 195, 210, 139, 222, 20, 185, 19, 22, 97, 221, 216, 14, 20, 117, 106, 114, 15, 172, 151, 155, 86, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}