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: 9b673410a8a60599f3f974864a00d7455425a797f60219992c8412c1cc9109c3
Tx prefix hash: 0da64a9f906647116d7e172170f59b5eb6acaa608027fd880d5c4d84cd7033ce
Tx public key: 86983ac31ae011406c81256d3c2ca099eeb432c34bec55151d3b0fbe631ee18d
| Timestamp: 1779433682 | Timestamp [UTC]: 2026-05-22 07:08:02 | Age [y:d:h:m:s]: 00:017:19:41:46 |
| Block: 56 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0908 kB |
| Tx version: 2 | No of confirmations: 7853 | RingCT/type: yes/0 |
| Extra: 0186983ac31ae011406c81256d3c2ca099eeb432c34bec55151d3b0fbe631ee18d020900000002a662ed0300 | ||
1 output(s) for total of 35.180681291499 HMNY
| stealth address | amount | amount idx | tag |
| 00: c5dcf3d4ec3a94411414100fc7f706e05804763460bf860b8276df8356ab9a5e | 35.180681291499 | 52 of 0 | <81> |
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": 116,
"vin": [ {
"gen": {
"height": 56
}
}
],
"vout": [ {
"amount": 35180681291499,
"target": {
"tagged_key": {
"key": "c5dcf3d4ec3a94411414100fc7f706e05804763460bf860b8276df8356ab9a5e",
"view_tag": "81"
}
}
}
],
"extra": [ 1, 134, 152, 58, 195, 26, 224, 17, 64, 108, 129, 37, 109, 60, 44, 160, 153, 238, 180, 50, 195, 75, 236, 85, 21, 29, 59, 15, 190, 99, 30, 225, 141, 2, 9, 0, 0, 0, 2, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}