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: 42090586143a271f577e27c9670591b817d2218d8d22770d0261782dc2b32ba7
Tx prefix hash: 769d8e19082351ce34e8df48264c970a916a43103af8decdde3f219a0c89714b
Tx public key: 51491b8f8d8fb9cd8c8701cf5fc99a95b84a5a7a6b5b38df7cbc058d77e89619
| Timestamp: 1780897842 | Timestamp [UTC]: 2026-06-08 05:50:42 | Age [y:d:h:m:s]: 00:000:17:28:11 |
| Block: 7780 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 106 | RingCT/type: yes/0 |
| Extra: 0151491b8f8d8fb9cd8c8701cf5fc99a95b84a5a7a6b5b38df7cbc058d77e896190209000000014a728a4c00 | ||
1 output(s) for total of 34.674418683997 HMNY
| stealth address | amount | amount idx | tag |
| 00: 66bcb465faaddd28fbd7512ba65cc9e6d46ea5c1528e1ef6f28b668ae56d76ba | 34.674418683997 | 9640 of 0 | <1b> |
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": 7840,
"vin": [ {
"gen": {
"height": 7780
}
}
],
"vout": [ {
"amount": 34674418683997,
"target": {
"tagged_key": {
"key": "66bcb465faaddd28fbd7512ba65cc9e6d46ea5c1528e1ef6f28b668ae56d76ba",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 81, 73, 27, 143, 141, 143, 185, 205, 140, 135, 1, 207, 95, 201, 154, 149, 184, 74, 90, 122, 107, 91, 56, 223, 124, 188, 5, 141, 119, 232, 150, 25, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}