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: 9e40ee211068d71f06d77a6a287b286f98538771ac2d69076509d7724d691c34
Tx prefix hash: a1df31569d5047a50802ac036940ae49b14e55533c1e8734b2db29906c55261f
Tx public key: 40d5f1c0e6f50631e4ed74c5089a8266b80abf94f4c09cdf84e2461c6734a320
| Timestamp: 1780774722 | Timestamp [UTC]: 2026-06-06 19:38:42 | Age [y:d:h:m:s]: 00:002:05:08:05 |
| Block: 6705 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1181 | RingCT/type: yes/0 |
| Extra: 0140d5f1c0e6f50631e4ed74c5089a8266b80abf94f4c09cdf84e2461c6734a320020900000003e49593ff00 | ||
1 output(s) for total of 34.737338011589 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0e670b5c04649e8fbe717315463867c096ce17f183620fd0922cfdae8ee5f199 | 34.737338011589 | 8269 of 0 | <42> |
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": 6765,
"vin": [ {
"gen": {
"height": 6705
}
}
],
"vout": [ {
"amount": 34737338011589,
"target": {
"tagged_key": {
"key": "0e670b5c04649e8fbe717315463867c096ce17f183620fd0922cfdae8ee5f199",
"view_tag": "42"
}
}
}
],
"extra": [ 1, 64, 213, 241, 192, 230, 245, 6, 49, 228, 237, 116, 197, 8, 154, 130, 102, 184, 10, 191, 148, 244, 192, 156, 223, 132, 226, 70, 28, 103, 52, 163, 32, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}