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: b274b64f6bea3f2146fc382cbe3d944f49f5382ceb6a3de992b4d0c0ba3ee4c7
Tx prefix hash: f74f900187134efa5b3790a51d88bbcb101fd5601cd4a7978d7263bc04746120
Tx public key: 605d92243ecc2e8476d927dd91b0c4c217d30e7584d352ea47cf0e6714f972af
| Timestamp: 1779434684 | Timestamp [UTC]: 2026-05-22 07:24:44 | Age [y:d:h:m:s]: 00:017:19:15:52 |
| Block: 97 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7799 | RingCT/type: yes/0 |
| Extra: 01605d92243ecc2e8476d927dd91b0c4c217d30e7584d352ea47cf0e6714f972af020900000001a662ed0300 | ||
1 output(s) for total of 35.177930221646 HMNY
| stealth address | amount | amount idx | tag |
| 00: d47acade1402103c6ad1da1af396a7c3cbd52ecaa183ebedbeb4026203b330db | 35.177930221646 | 93 of 0 | <c4> |
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": 157,
"vin": [ {
"gen": {
"height": 97
}
}
],
"vout": [ {
"amount": 35177930221646,
"target": {
"tagged_key": {
"key": "d47acade1402103c6ad1da1af396a7c3cbd52ecaa183ebedbeb4026203b330db",
"view_tag": "c4"
}
}
}
],
"extra": [ 1, 96, 93, 146, 36, 62, 204, 46, 132, 118, 217, 39, 221, 145, 176, 196, 194, 23, 211, 14, 117, 132, 211, 82, 234, 71, 207, 14, 103, 20, 249, 114, 175, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}