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: 3eb5224f586644ce7462ad42095e01b61d19df80758a36e001fe1dd17693534f
Tx prefix hash: 0d7dc630cc429c4396bf8f298147039288f086602baa7a88d886b46d492f034e
Tx public key: ae14550e1834e3e27e1bb7d9e7fac7d8caa04df62e895a38a5a9d15c5f72b7f9
| Timestamp: 1779997373 | Timestamp [UTC]: 2026-05-28 19:42:53 | Age [y:d:h:m:s]: 00:011:07:06:55 |
| Block: 4036 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3884 | RingCT/type: yes/0 |
| Extra: 01ae14550e1834e3e27e1bb7d9e7fac7d8caa04df62e895a38a5a9d15c5f72b7f902090000000226697be300 | ||
1 output(s) for total of 34.917245296853 HMNY
| stealth address | amount | amount idx | tag |
| 00: 29793f38426b4a7889cdd55d80821480031950dcb21985cfadb8b3a93b122aca | 34.917245296853 | 4995 of 0 | <89> |
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": 4096,
"vin": [ {
"gen": {
"height": 4036
}
}
],
"vout": [ {
"amount": 34917245296853,
"target": {
"tagged_key": {
"key": "29793f38426b4a7889cdd55d80821480031950dcb21985cfadb8b3a93b122aca",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 174, 20, 85, 14, 24, 52, 227, 226, 126, 27, 183, 217, 231, 250, 199, 216, 202, 160, 77, 246, 46, 137, 90, 56, 165, 169, 209, 92, 95, 114, 183, 249, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}