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: 3aa11d26c960197c44e7e381e93d1fb7c6f70730017a7c2903fc234c117111c4
Tx prefix hash: bec31249250733b73b3f980367018defd179cefc65cc1b10d9f8cc0f07971250
Tx public key: fe58a1659009ed2a894635d914fc36fd7b60acf1d52ad15694f1a8427fc675d3
| Timestamp: 1780905959 | Timestamp [UTC]: 2026-06-08 08:05:59 | Age [y:d:h:m:s]: 00:000:12:02:12 |
| Block: 7867 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 19 | RingCT/type: yes/0 |
| Extra: 01fe58a1659009ed2a894635d914fc36fd7b60acf1d52ad15694f1a8427fc675d30209000000034a728a4c00 | ||
1 output(s) for total of 34.660433472138 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9faa19969f63ccc6d5df5a784164fe59fdaa4f1cd623f4f85ae32ec018a52954 | 34.660433472138 | 9753 of 0 | <8e> |
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": 7927,
"vin": [ {
"gen": {
"height": 7867
}
}
],
"vout": [ {
"amount": 34660433472138,
"target": {
"tagged_key": {
"key": "9faa19969f63ccc6d5df5a784164fe59fdaa4f1cd623f4f85ae32ec018a52954",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 254, 88, 161, 101, 144, 9, 237, 42, 137, 70, 53, 217, 20, 252, 54, 253, 123, 96, 172, 241, 213, 42, 209, 86, 148, 241, 168, 66, 127, 198, 117, 211, 2, 9, 0, 0, 0, 3, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}