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: faa160ef142545e4f6fec7b96bbc8865d442ebeab8f40f613047c28be4b13361
Tx prefix hash: 1bff33f15f4396895fd3f6254eac2a07cae21579a62b5c5056cacaa38162f8f7
Tx public key: 70bc672f2addf25d6a6e010e636bd188cfd62a7e1ceb7bd25684d822b41f0529
| Timestamp: 1779435044 | Timestamp [UTC]: 2026-05-22 07:30:44 | Age [y:d:h:m:s]: 00:018:09:38:19 |
| Block: 115 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 8619 | RingCT/type: yes/0 |
| Extra: 0170bc672f2addf25d6a6e010e636bd188cfd62a7e1ceb7bd25684d822b41f0529020900000001a662ed0300 | ||
1 output(s) for total of 35.176722502839 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9b4755177f1f89810a2ef0430d336951329a196f3d82f15c417ee3c4f5b2f744 | 35.176722502839 | 111 of 0 | <64> |
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": 175,
"vin": [ {
"gen": {
"height": 115
}
}
],
"vout": [ {
"amount": 35176722502839,
"target": {
"tagged_key": {
"key": "9b4755177f1f89810a2ef0430d336951329a196f3d82f15c417ee3c4f5b2f744",
"view_tag": "64"
}
}
}
],
"extra": [ 1, 112, 188, 103, 47, 42, 221, 242, 93, 106, 110, 1, 14, 99, 107, 209, 136, 207, 214, 42, 126, 28, 235, 123, 210, 86, 132, 216, 34, 180, 31, 5, 41, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}