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: db8b4845536b2331018ce74a55592fdcfab85f9de49c4be2ffa640737ff322bb
Tx prefix hash: 576fcd1c6c45b26a01f15adbe02a7b98c30f67cbe5682ea666c12cbfbd67f5f4
Tx public key: 8c58e3baac5a7ecc9d81110c6258aebe9e6b5ea65c2837751281de71acddab17
| Timestamp: 1779724696 | Timestamp [UTC]: 2026-05-25 15:58:16 | Age [y:d:h:m:s]: 00:014:10:42:20 |
| Block: 1831 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6065 | RingCT/type: yes/0 |
| Extra: 018c58e3baac5a7ecc9d81110c6258aebe9e6b5ea65c2837751281de71acddab17020900000002ba6d17be00 | ||
1 output(s) for total of 35.061776831561 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6d72d9e171631776ed9210eb2f18345cd53b4c42480c6021f7eff66d45b41689 | 35.061776831561 | 2025 of 0 | <00> |
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": 1891,
"vin": [ {
"gen": {
"height": 1831
}
}
],
"vout": [ {
"amount": 35061776831561,
"target": {
"tagged_key": {
"key": "6d72d9e171631776ed9210eb2f18345cd53b4c42480c6021f7eff66d45b41689",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 140, 88, 227, 186, 172, 90, 126, 204, 157, 129, 17, 12, 98, 88, 174, 190, 158, 107, 94, 166, 92, 40, 55, 117, 18, 129, 222, 113, 172, 221, 171, 23, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}