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: 0e00bbcee895936b206916bcbc0373ddb7c7ed467cac1d5b4f2796d617f628aa
Tx prefix hash: 91589bf97c5cba92f36604edb13a50a87f6232e5f6eb04fd3cd30a1c6510c34b
Tx public key: 62f8410307a232c0f1fd5f61fa2bc0e6d64df04dd071c1cb9f3424eafbaf85c9
| Timestamp: 1780395638 | Timestamp [UTC]: 2026-06-02 10:20:38 | Age [y:d:h:m:s]: 00:006:16:19:58 |
| Block: 5247 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2649 | RingCT/type: yes/0 |
| Extra: 0162f8410307a232c0f1fd5f61fa2bc0e6d64df04dd071c1cb9f3424eafbaf85c902090000000126697be300 | ||
1 output(s) for total of 34.834074109151 HMNY
| stealth address | amount | amount idx | tag |
| 00: f78215584bb1b27bcff3bd1ea70530875335cda80e10bfce8f32c7fa904f44dd | 34.834074109151 | 6644 of 0 | <86> |
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": 5307,
"vin": [ {
"gen": {
"height": 5247
}
}
],
"vout": [ {
"amount": 34834074109151,
"target": {
"tagged_key": {
"key": "f78215584bb1b27bcff3bd1ea70530875335cda80e10bfce8f32c7fa904f44dd",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 98, 248, 65, 3, 7, 162, 50, 192, 241, 253, 95, 97, 250, 43, 192, 230, 214, 77, 240, 77, 208, 113, 193, 203, 159, 52, 36, 234, 251, 175, 133, 201, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}