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: 62b63c6c91769c21ef5d2cecbdc497f9876cef8a2f95274d0b6787840e3360ac
Tx prefix hash: 79aa5d73436f84c3a1d45d75741708a807436ac7e8d7cbb0e15d80c66d606c92
Tx public key: 2e1defa90fbc47e7359c3f7539d6ae423f464d86df6470d93abf94a32a07428d
| Timestamp: 1780019562 | Timestamp [UTC]: 2026-05-29 01:52:42 | Age [y:d:h:m:s]: 00:010:23:43:15 |
| Block: 4135 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3751 | RingCT/type: yes/0 |
| Extra: 012e1defa90fbc47e7359c3f7539d6ae423f464d86df6470d93abf94a32a07428d02090000000126697be300 | ||
1 output(s) for total of 34.908034670761 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6e7d5f5218d670064fee38610048e1aab5d7beb8abf273856b77c89d40586fb6 | 34.908034670761 | 5166 of 0 | <a1> |
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": 4195,
"vin": [ {
"gen": {
"height": 4135
}
}
],
"vout": [ {
"amount": 34908034670761,
"target": {
"tagged_key": {
"key": "6e7d5f5218d670064fee38610048e1aab5d7beb8abf273856b77c89d40586fb6",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 46, 29, 239, 169, 15, 188, 71, 231, 53, 156, 63, 117, 57, 214, 174, 66, 63, 70, 77, 134, 223, 100, 112, 217, 58, 191, 148, 163, 42, 7, 66, 141, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}