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: a810a9e1bdf53cd4bb36b9a0df0f494a6044e8cdc433c57f4c09a7d2ff65a121
Tx prefix hash: 434d126a84e8b20e8da4272d91c21129ab4e64248091850f697369e2ca96cde4
Tx public key: 90c1582e07f7600742d0911377c1699f9dab1cb9add15c5b04905d011e3669d9
| Timestamp: 1779647339 | Timestamp [UTC]: 2026-05-24 18:28:59 | Age [y:d:h:m:s]: 00:015:07:06:58 |
| Block: 1459 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6427 | RingCT/type: yes/0 |
| Extra: 0190c1582e07f7600742d0911377c1699f9dab1cb9add15c5b04905d011e3669d9020900000004ba6d17be00 | ||
1 output(s) for total of 35.086663195050 HMNY
| stealth address | amount | amount idx | tag |
| 00: be1404992d4d394ffc1dc8ea0a6a4bb37a967c646fb499d53b734b238a0f49fc | 35.086663195050 | 1613 of 0 | <54> |
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": 1519,
"vin": [ {
"gen": {
"height": 1459
}
}
],
"vout": [ {
"amount": 35086663195050,
"target": {
"tagged_key": {
"key": "be1404992d4d394ffc1dc8ea0a6a4bb37a967c646fb499d53b734b238a0f49fc",
"view_tag": "54"
}
}
}
],
"extra": [ 1, 144, 193, 88, 46, 7, 247, 96, 7, 66, 208, 145, 19, 119, 193, 105, 159, 157, 171, 28, 185, 173, 209, 92, 91, 4, 144, 93, 1, 30, 54, 105, 217, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}