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: e74ccd55097521b00930305a3bfa508e1cc17c5fd4c59eb8e05b20ebfc00113c
Tx prefix hash: 8b69bfa634dab191f10590318f78eb19165752a1699628c37e3743c469a0fcde
Tx public key: 62ba4aa0f1abaae0536b8566168cda8c2fcdfb4f3502e7e38241652e7a9b7c78
| Timestamp: 1779632271 | Timestamp [UTC]: 2026-05-24 14:17:51 | Age [y:d:h:m:s]: 00:015:10:28:56 |
| Block: 945 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6941 | RingCT/type: yes/0 |
| Extra: 0162ba4aa0f1abaae0536b8566168cda8c2fcdfb4f3502e7e38241652e7a9b7c78020900000001ba6d17be00 | ||
1 output(s) for total of 35.121078259511 HMNY
| stealth address | amount | amount idx | tag |
| 00: 508200f799146013129db525c9438007a8b6349c7749d4dd6b3e5b7e62f92a17 | 35.121078259511 | 1079 of 0 | <fa> |
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": 1005,
"vin": [ {
"gen": {
"height": 945
}
}
],
"vout": [ {
"amount": 35121078259511,
"target": {
"tagged_key": {
"key": "508200f799146013129db525c9438007a8b6349c7749d4dd6b3e5b7e62f92a17",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 98, 186, 74, 160, 241, 171, 170, 224, 83, 107, 133, 102, 22, 140, 218, 140, 47, 205, 251, 79, 53, 2, 231, 227, 130, 65, 101, 46, 122, 155, 124, 120, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}