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: 30ad935f7eedb52db5736ff1638f016b3d9936389b12aa9cf8b36aba6406611e
Tx prefix hash: 14bd0414640e5564ba8d4d9c3a97350c825a0293bfd73c8456161e14a8e3b4fa
Tx public key: 14add2892c36402837f843909c0e2feaf11e84e86fe34e1b17bf5691292fbddf
| Timestamp: 1779480434 | Timestamp [UTC]: 2026-05-22 20:07:14 | Age [y:d:h:m:s]: 00:017:04:39:33 |
| Block: 644 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7242 | RingCT/type: yes/0 |
| Extra: 0114add2892c36402837f843909c0e2feaf11e84e86fe34e1b17bf5691292fbddf02090000000293369e7d00 | ||
1 output(s) for total of 35.141247498213 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9d619710f5c72fbb38ba6ba2f4c441a2995d5570d49fdd6cd7f0ad759800a6c | 35.141247498213 | 687 of 0 | <57> |
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": 704,
"vin": [ {
"gen": {
"height": 644
}
}
],
"vout": [ {
"amount": 35141247498213,
"target": {
"tagged_key": {
"key": "d9d619710f5c72fbb38ba6ba2f4c441a2995d5570d49fdd6cd7f0ad759800a6c",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 20, 173, 210, 137, 44, 54, 64, 40, 55, 248, 67, 144, 156, 14, 47, 234, 241, 30, 132, 232, 111, 227, 78, 27, 23, 191, 86, 145, 41, 47, 189, 223, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}