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: 508e2bad5ade2f68f22829c63f472eacd25fcce03a9f07b67bd1930bf4a97048
Tx prefix hash: 9b3859ef58f40e7b37ead03717398248b44701c2b374e960200792d4b60c0cd7
Tx public key: 62ebfddbf43de4af37fe936a6eb0d3578fbaae7353d9700605fee665a27328e0
| Timestamp: 1779889283 | Timestamp [UTC]: 2026-05-27 13:41:23 | Age [y:d:h:m:s]: 00:012:13:57:27 |
| Block: 3047 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4895 | RingCT/type: yes/0 |
| Extra: 0162ebfddbf43de4af37fe936a6eb0d3578fbaae7353d9700605fee665a27328e002090000000226697be300 | ||
1 output(s) for total of 34.980550946529 HMNY
| stealth address | amount | amount idx | tag |
| 00: 54e1ce4d270c73b7202ad1a4ecb0e44fbf66f71353b11cd1373eb88ab6b15013 | 34.980550946529 | 3623 of 0 | <22> |
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": 3107,
"vin": [ {
"gen": {
"height": 3047
}
}
],
"vout": [ {
"amount": 34980550946529,
"target": {
"tagged_key": {
"key": "54e1ce4d270c73b7202ad1a4ecb0e44fbf66f71353b11cd1373eb88ab6b15013",
"view_tag": "22"
}
}
}
],
"extra": [ 1, 98, 235, 253, 219, 244, 61, 228, 175, 55, 254, 147, 106, 110, 176, 211, 87, 143, 186, 174, 115, 83, 217, 112, 6, 5, 254, 230, 101, 162, 115, 40, 224, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}