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: 6f601340d2dc89f43e47b9d1a14766db1632c84832c2d9663c4b61df34a82357
Tx prefix hash: 8825346be5afef1a7cda1f35a3dc25dedefd35a3db2b7e6ab163ac0f2b62c485
Tx public key: 95752c784e50dcca2c0081631330e62e84ac50d227e2485b9cc042c506f465a4
| Timestamp: 1781022232 | Timestamp [UTC]: 2026-06-09 16:23:52 | Age [y:d:h:m:s]: 00:006:08:49:15 |
| Block: 8706 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 39 | RingCT/type: yes/0 |
| Extra: 0195752c784e50dcca2c0081631330e62e84ac50d227e2485b9cc042c506f465a4020900000002e49593ff00 | ||
1 output(s) for total of 34.605011879740 HMNY
| stealth address | amount | amount idx | tag |
| 00: 31e5642d279ece4e94b6aa997012a1f31e5c321000173bd5046817d2b1db76f8 | 34.605011879740 | 10766 of 0 | <50> |
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": 8766,
"vin": [ {
"gen": {
"height": 8706
}
}
],
"vout": [ {
"amount": 34605011879740,
"target": {
"tagged_key": {
"key": "31e5642d279ece4e94b6aa997012a1f31e5c321000173bd5046817d2b1db76f8",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 149, 117, 44, 120, 78, 80, 220, 202, 44, 0, 129, 99, 19, 48, 230, 46, 132, 172, 80, 210, 39, 226, 72, 91, 156, 192, 66, 197, 6, 244, 101, 164, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}