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: 1c1e5ef4046c7b20ad96e534eccd85cdf4280bd5331d6fd92d281fbce89cb3b5
Tx prefix hash: e6ce02d1e3dbf7581c4624ad1bca4748a7572c77eb118f272e48acddb8df882d
Tx public key: f047eddc5f719a196070b1720c2c269618e5174a518a69ce953e0bc2b965f4cc
| Timestamp: 1780030697 | Timestamp [UTC]: 2026-05-29 04:58:17 | Age [y:d:h:m:s]: 00:010:20:37:40 |
| Block: 4198 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3688 | RingCT/type: yes/0 |
| Extra: 01f047eddc5f719a196070b1720c2c269618e5174a518a69ce953e0bc2b965f4cc02090000000226697be300 | ||
1 output(s) for total of 34.932064265863 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3a67174b9e01e938f593322c867fecd1946aa2f2cc96ee5f9dcb35a9bc4bed6a | 34.932064265863 | 5231 of 0 | <a5> |
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": 4258,
"vin": [ {
"gen": {
"height": 4198
}
}
],
"vout": [ {
"amount": 34932064265863,
"target": {
"tagged_key": {
"key": "3a67174b9e01e938f593322c867fecd1946aa2f2cc96ee5f9dcb35a9bc4bed6a",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 240, 71, 237, 220, 95, 113, 154, 25, 96, 112, 177, 114, 12, 44, 38, 150, 24, 229, 23, 74, 81, 138, 105, 206, 149, 62, 11, 194, 185, 101, 244, 204, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}