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: 04b360ad9d900c3140d0466b3374fe98e03509fa5ec20776e6410a4757f7b833
Tx prefix hash: c4e1d1dedfb4a585825930b3e5b7d3390645bda46cea594275d30e4b3f9d01a5
Tx public key: df357f6c63a6a4c31a1c3615aa75b986b8e3d684613dc96ef13d5605b3f691ea
| Timestamp: 1779713504 | Timestamp [UTC]: 2026-05-25 12:51:44 | Age [y:d:h:m:s]: 00:014:10:27:09 |
| Block: 1596 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6290 | RingCT/type: yes/0 |
| Extra: 01df357f6c63a6a4c31a1c3615aa75b986b8e3d684613dc96ef13d5605b3f691ea020900000003ba6d17be00 | ||
1 output(s) for total of 35.077496001711 HMNY
| stealth address | amount | amount idx | tag |
| 00: 85602aee1b1063b4def1093c148f03ebc3b1a26ed6db0ff3e039c19aae04489d | 35.077496001711 | 1754 of 0 | <a7> |
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": 1656,
"vin": [ {
"gen": {
"height": 1596
}
}
],
"vout": [ {
"amount": 35077496001711,
"target": {
"tagged_key": {
"key": "85602aee1b1063b4def1093c148f03ebc3b1a26ed6db0ff3e039c19aae04489d",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 223, 53, 127, 108, 99, 166, 164, 195, 26, 28, 54, 21, 170, 117, 185, 134, 184, 227, 214, 132, 97, 61, 201, 110, 241, 61, 86, 5, 179, 246, 145, 234, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}