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: 262d56e11787ce7826b0826386fb0fb7df3e461993197c5434bec5cef20a24a0
Tx prefix hash: 45dd763e554d3eae1f3fb77ca8dc5760c79fb33d1daab9670d0d32830f66a126
Tx public key: f2d49b470cdabca06ba67d5d2785e9dc84a12187b07df6494de29b27cb7cd059
| Timestamp: 1780683488 | Timestamp [UTC]: 2026-06-05 18:18:08 | Age [y:d:h:m:s]: 00:003:06:28:39 |
| Block: 5325 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2561 | RingCT/type: yes/0 |
| Extra: 01f2d49b470cdabca06ba67d5d2785e9dc84a12187b07df6494de29b27cb7cd059020900000002e49593ff00 | ||
1 output(s) for total of 34.828892113247 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8c48c94c210ea768d4d22899d001c3b1ea5ff5723e52f1c3843b30b6cd1e3f7d | 34.828892113247 | 6754 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": 5385,
"vin": [ {
"gen": {
"height": 5325
}
}
],
"vout": [ {
"amount": 34828892113247,
"target": {
"tagged_key": {
"key": "8c48c94c210ea768d4d22899d001c3b1ea5ff5723e52f1c3843b30b6cd1e3f7d",
"view_tag": "c4"
}
}
}
],
"extra": [ 1, 242, 212, 155, 71, 12, 218, 188, 160, 107, 166, 125, 93, 39, 133, 233, 220, 132, 161, 33, 135, 176, 125, 246, 73, 77, 226, 155, 39, 203, 124, 208, 89, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}