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: cc1817a2219dbbda5ff0a2940a0d24455165e39730da7f57de101a1520b07369
Tx prefix hash: f4bbf91ab7c4d19b30fb9c73f23407a132ef70655b0fd1be023f34efd6fe95d0
Tx public key: fba3b17d9bb07bbb0f2c882a93912a2afce228d57695b7e7a1f5639ab51b6b85
| Timestamp: 1779450319 | Timestamp [UTC]: 2026-05-22 11:45:19 | Age [y:d:h:m:s]: 00:017:13:50:38 |
| Block: 315 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7571 | RingCT/type: yes/0 |
| Extra: 01fba3b17d9bb07bbb0f2c882a93912a2afce228d57695b7e7a1f5639ab51b6b850209000000024438f87f00 | ||
1 output(s) for total of 35.163306194450 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2efaed310e3e508fd41416af502c435ad1253eb9bd185f0996ce9d861cf198b2 | 35.163306194450 | 311 of 0 | <79> |
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": 375,
"vin": [ {
"gen": {
"height": 315
}
}
],
"vout": [ {
"amount": 35163306194450,
"target": {
"tagged_key": {
"key": "2efaed310e3e508fd41416af502c435ad1253eb9bd185f0996ce9d861cf198b2",
"view_tag": "79"
}
}
}
],
"extra": [ 1, 251, 163, 177, 125, 155, 176, 123, 187, 15, 44, 136, 42, 147, 145, 42, 42, 252, 226, 40, 213, 118, 149, 183, 231, 161, 245, 99, 154, 181, 27, 107, 133, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}