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: ddc41cf10e2a05aa0eb3fa597a5d25fbd19e9daa957f925333e17873ba89e311
Tx prefix hash: 04c93ba55e8d5cd3d466676e076e0c3ac09a0d1206adee78e17688a37e78fe9e
Tx public key: 9de6b2c11ccad7fc3e9084dfe288d1e28b50b94d4059d3aea6a01de424c0185d
| Timestamp: 1779923347 | Timestamp [UTC]: 2026-05-27 23:09:07 | Age [y:d:h:m:s]: 00:012:01:37:40 |
| Block: 3365 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4521 | RingCT/type: yes/0 |
| Extra: 019de6b2c11ccad7fc3e9084dfe288d1e28b50b94d4059d3aea6a01de424c0185d02090000000226697be300 | ||
1 output(s) for total of 34.959340365736 HMNY
| stealth address | amount | amount idx | tag |
| 00: e0717dd29eeea663660dba6c2ffc71046dba9e30f3da29b805889d6a454e9917 | 34.959340365736 | 4056 of 0 | <76> |
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": 3425,
"vin": [ {
"gen": {
"height": 3365
}
}
],
"vout": [ {
"amount": 34959340365736,
"target": {
"tagged_key": {
"key": "e0717dd29eeea663660dba6c2ffc71046dba9e30f3da29b805889d6a454e9917",
"view_tag": "76"
}
}
}
],
"extra": [ 1, 157, 230, 178, 193, 28, 202, 215, 252, 62, 144, 132, 223, 226, 136, 209, 226, 139, 80, 185, 77, 64, 89, 211, 174, 166, 160, 29, 228, 36, 192, 24, 93, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}