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: 6f5fcd865866074f2d7f0dd305d1b0c690cc0d2d8dfa547ee037c12ec5976831
Tx prefix hash: 689b0ebd37e27aecb090aa7ef3ba62feb922b875085c14720c6dc5e4ee4910df
Tx public key: 62ffa5519cf06e2e7e479655984b00f51810f69dfc86c49d6d87f53863e6740f
| Timestamp: 1779893443 | Timestamp [UTC]: 2026-05-27 14:50:43 | Age [y:d:h:m:s]: 00:012:10:45:14 |
| Block: 3079 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4807 | RingCT/type: yes/0 |
| Extra: 0162ffa5519cf06e2e7e479655984b00f51810f69dfc86c49d6d87f53863e6740f02090000000726697be300 | ||
1 output(s) for total of 34.978415966255 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4fc6110ef6aef6acb0baac290b96e2ee7ba37d725c15de1fa8cd74590bd0cb57 | 34.978415966255 | 3669 of 0 | <1a> |
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": 3139,
"vin": [ {
"gen": {
"height": 3079
}
}
],
"vout": [ {
"amount": 34978415966255,
"target": {
"tagged_key": {
"key": "4fc6110ef6aef6acb0baac290b96e2ee7ba37d725c15de1fa8cd74590bd0cb57",
"view_tag": "1a"
}
}
}
],
"extra": [ 1, 98, 255, 165, 81, 156, 240, 110, 46, 126, 71, 150, 85, 152, 75, 0, 245, 24, 16, 246, 157, 252, 134, 196, 157, 109, 135, 245, 56, 99, 230, 116, 15, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}