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: 0006b62e7dcc73c7bdf79dcf4818c93a4e282dfc28e2ca9ddddc11641e6aecd1
Tx prefix hash: e50a87e94f997080138783ffb66ace65b279fd02cf4f95c3037627820736be55
Tx public key: 549d9016250df80913359cac6f7df51334888c5c713b94ee2a999d6b506e917a
| Timestamp: 1779865868 | Timestamp [UTC]: 2026-05-27 07:11:08 | Age [y:d:h:m:s]: 00:017:04:09:57 |
| Block: 2743 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6002 | RingCT/type: yes/0 |
| Extra: 01549d9016250df80913359cac6f7df51334888c5c713b94ee2a999d6b506e917a02090000000426697be300 | ||
1 output(s) for total of 35.000839759612 HMNY
| stealth address | amount | amount idx | tag |
| 00: fbcda9d82c5ff29bf4e5a8b0fc8e36767032bddfe497463727db1b4ca431260c | 35.000839759612 | 3241 of 0 | <55> |
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": 2803,
"vin": [ {
"gen": {
"height": 2743
}
}
],
"vout": [ {
"amount": 35000839759612,
"target": {
"tagged_key": {
"key": "fbcda9d82c5ff29bf4e5a8b0fc8e36767032bddfe497463727db1b4ca431260c",
"view_tag": "55"
}
}
}
],
"extra": [ 1, 84, 157, 144, 22, 37, 13, 248, 9, 19, 53, 156, 172, 111, 125, 245, 19, 52, 136, 140, 92, 113, 59, 148, 238, 42, 153, 157, 107, 80, 110, 145, 122, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}