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: d7ba148fac89c979237647970d16bc88ee7b23defa5f212b841956dcbdf45c14
Tx prefix hash: 0f9ff02e09bd3e93772ea92e327eb662932965a774c8457b56d4cc60867e88a3
Tx public key: 934ab5006662fb14b1f380013c26e1752ec941ec605cef179743926f9daa3ae8
| Timestamp: 1779461940 | Timestamp [UTC]: 2026-05-22 14:59:00 | Age [y:d:h:m:s]: 00:017:10:36:57 |
| Block: 454 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7432 | RingCT/type: yes/0 |
| Extra: 01934ab5006662fb14b1f380013c26e1752ec941ec605cef179743926f9daa3ae80208d803fa4069937647 | ||
1 output(s) for total of 35.153984874180 HMNY
| stealth address | amount | amount idx | tag |
| 00: 68f7ebcf3ca87bdb252ec3677196db1c26eb6dbacd80901f331ece4c14b50786 | 35.153984874180 | 458 of 0 | <60> |
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": 514,
"vin": [ {
"gen": {
"height": 454
}
}
],
"vout": [ {
"amount": 35153984874180,
"target": {
"tagged_key": {
"key": "68f7ebcf3ca87bdb252ec3677196db1c26eb6dbacd80901f331ece4c14b50786",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 147, 74, 181, 0, 102, 98, 251, 20, 177, 243, 128, 1, 60, 38, 225, 117, 46, 201, 65, 236, 96, 92, 239, 23, 151, 67, 146, 111, 157, 170, 58, 232, 2, 8, 216, 3, 250, 64, 105, 147, 118, 71
],
"rct_signatures": {
"type": 0
}
}