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: a8088950b2f1bdda91ea60c5421fb8bdf262622e7e9c940936ffbc04e6b6096d
Tx prefix hash: 03719fca517b5c0ea926852facb6a6a5b57a7e834db3bab531700d46e5640553
Tx public key: fd620a951d1d53e856720da3d19736645bb1f4f45eb5bdfd09a945886d9a9f4a
| Timestamp: 1779436860 | Timestamp [UTC]: 2026-05-22 08:01:00 | Age [y:d:h:m:s]: 00:017:17:34:57 |
| Block: 148 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7738 | RingCT/type: yes/0 |
| Extra: 01fd620a951d1d53e856720da3d19736645bb1f4f45eb5bdfd09a945886d9a9f4a020900000002a662ed0300 | ||
1 output(s) for total of 35.174508459379 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0cc31f560a2f84db0080d4722f1caf29f19b071ca4514db696364443ba8706d9 | 35.174508459379 | 144 of 0 | <c6> |
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": 208,
"vin": [ {
"gen": {
"height": 148
}
}
],
"vout": [ {
"amount": 35174508459379,
"target": {
"tagged_key": {
"key": "0cc31f560a2f84db0080d4722f1caf29f19b071ca4514db696364443ba8706d9",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 253, 98, 10, 149, 29, 29, 83, 232, 86, 114, 13, 163, 209, 151, 54, 100, 91, 177, 244, 244, 94, 181, 189, 253, 9, 169, 69, 136, 109, 154, 159, 74, 2, 9, 0, 0, 0, 2, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}