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: 18c0e5cfd8dce23b7a7b7454562aa1cc4fe2dc87ed00cf025eb0d05c255ce806
Tx prefix hash: c9b0532bd7b9f194be5c5462258a9696b2aaf88f7fdd79ea6da3305127c1067c
Tx public key: bcf50d626dd597f32ded9f2c369e46baef7cafc94b1fdf69c57f16099e749756
| Timestamp: 1780867188 | Timestamp [UTC]: 2026-06-07 21:19:48 | Age [y:d:h:m:s]: 00:001:01:05:01 |
| Block: 7680 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 206 | RingCT/type: yes/0 |
| Extra: 01bcf50d626dd597f32ded9f2c369e46baef7cafc94b1fdf69c57f16099e749756020900000001e49593ff00 | ||
1 output(s) for total of 34.681022971067 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6107a07c355980c17a8035a5d3c24199e866faafb13fdbd4ee41ffd1229a4ca1 | 34.681022971067 | 9496 of 0 | <3f> |
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": 7740,
"vin": [ {
"gen": {
"height": 7680
}
}
],
"vout": [ {
"amount": 34681022971067,
"target": {
"tagged_key": {
"key": "6107a07c355980c17a8035a5d3c24199e866faafb13fdbd4ee41ffd1229a4ca1",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 188, 245, 13, 98, 109, 213, 151, 243, 45, 237, 159, 44, 54, 158, 70, 186, 239, 124, 175, 201, 75, 31, 223, 105, 197, 127, 22, 9, 158, 116, 151, 86, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}