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: a38a53fab23af24f26934f8bbf375ce0510bc4f247127f711ded2401b7d61782
Tx prefix hash: 3b1f1d3e9cc97d1f35af741d74507953e740e93dc5714863e46b4aa24d3e9dfe
Tx public key: 9f7c021c43aa094e1b421fdbfc5c08990b012cb8aae6f4ea4426386a98bdab78
| Timestamp: 1779848742 | Timestamp [UTC]: 2026-05-27 02:25:42 | Age [y:d:h:m:s]: 00:012:21:57:27 |
| Block: 2496 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5390 | RingCT/type: yes/0 |
| Extra: 019f7c021c43aa094e1b421fdbfc5c08990b012cb8aae6f4ea4426386a98bdab7802090000000226697be300 | ||
1 output(s) for total of 35.017333084718 HMNY
| stealth address | amount | amount idx | tag |
| 00: ffe69d40e1a2cfa6b1b1d65f816afaf9a7e2bde174c9d27791a5c4c6cd9c0f9a | 35.017333084718 | 2936 of 0 | <99> |
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": 2556,
"vin": [ {
"gen": {
"height": 2496
}
}
],
"vout": [ {
"amount": 35017333084718,
"target": {
"tagged_key": {
"key": "ffe69d40e1a2cfa6b1b1d65f816afaf9a7e2bde174c9d27791a5c4c6cd9c0f9a",
"view_tag": "99"
}
}
}
],
"extra": [ 1, 159, 124, 2, 28, 67, 170, 9, 78, 27, 66, 31, 219, 252, 92, 8, 153, 11, 1, 44, 184, 170, 230, 244, 234, 68, 38, 56, 106, 152, 189, 171, 120, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}