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: 92b11442464e7979fe3f0ed9d431878d56193d0b67c3613f773dee7f5b05936e
Tx prefix hash: 6843bca6346da491497e0941dec247c3c30e40dbfdca9c27db32bcfb30dcf9e4
Tx public key: e436baa1df977b864e9ca4698980c9f87c2fda5949c6da63575917bbecf22baa
| Timestamp: 1780691814 | Timestamp [UTC]: 2026-06-05 20:36:54 | Age [y:d:h:m:s]: 00:003:04:59:03 |
| Block: 5755 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2131 | RingCT/type: yes/0 |
| Extra: 01e436baa1df977b864e9ca4698980c9f87c2fda5949c6da63575917bbecf22baa020900000001e49593ff00 | ||
1 output(s) for total of 34.800338535772 HMNY
| stealth address | amount | amount idx | tag |
| 00: 987ef3e0ccff3c311ea60203e5f8c7c7641590cb9c7f05f5a11b1b16dcd86e34 | 34.800338535772 | 7208 of 0 | <61> |
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": 5815,
"vin": [ {
"gen": {
"height": 5755
}
}
],
"vout": [ {
"amount": 34800338535772,
"target": {
"tagged_key": {
"key": "987ef3e0ccff3c311ea60203e5f8c7c7641590cb9c7f05f5a11b1b16dcd86e34",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 228, 54, 186, 161, 223, 151, 123, 134, 78, 156, 164, 105, 137, 128, 201, 248, 124, 47, 218, 89, 73, 198, 218, 99, 87, 89, 23, 187, 236, 242, 43, 170, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}