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: 3c62b86a245c9b27b79b420c0aa0ed159c39e1a9d37702ca61dffd4394310caa
Tx prefix hash: bec97b0d086e7626849f365680c18fa074db5fb58bc602cc0f855af92758f4f3
Tx public key: e28d969d09cbdbd8b74e261d3a8ccebd5e46f8a4c3aaec17b66a769ad496a2d1
| Timestamp: 1781015578 | Timestamp [UTC]: 2026-06-09 14:32:58 | Age [y:d:h:m:s]: 00:006:01:40:55 |
| Block: 8628 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 117 | RingCT/type: yes/0 |
| Extra: 01e28d969d09cbdbd8b74e261d3a8ccebd5e46f8a4c3aaec17b66a769ad496a2d1020900000001e49593ff00 | ||
1 output(s) for total of 34.610160565758 HMNY
| stealth address | amount | amount idx | tag |
| 00: 927887983b8fa23fc6b1d3f3bc688e9183f2b0476bd58a4e116f11e37a2d8d36 | 34.610160565758 | 10666 of 0 | <e5> |
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": 8688,
"vin": [ {
"gen": {
"height": 8628
}
}
],
"vout": [ {
"amount": 34610160565758,
"target": {
"tagged_key": {
"key": "927887983b8fa23fc6b1d3f3bc688e9183f2b0476bd58a4e116f11e37a2d8d36",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 226, 141, 150, 157, 9, 203, 219, 216, 183, 78, 38, 29, 58, 140, 206, 189, 94, 70, 248, 164, 195, 170, 236, 23, 182, 106, 118, 154, 212, 150, 162, 209, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}