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: 91c96a7b16d56c3b035f19c9f5d74d2514517a0639a8454f7d79acafd07e93b6
Tx prefix hash: 03d3d072a6eebabbef1d1aa0134a6b180614c5316682eff15918812f7b563090
Tx public key: 8799b73ad7e7fd224bc198c67578c169838e332200f5c201b86af1fa032c535e
| Timestamp: 1780905235 | Timestamp [UTC]: 2026-06-08 07:53:55 | Age [y:d:h:m:s]: 00:000:13:18:12 |
| Block: 7859 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 27 | RingCT/type: yes/0 |
| Extra: 018799b73ad7e7fd224bc198c67578c169838e332200f5c201b86af1fa032c535e0209000000014a728a4c00 | ||
1 output(s) for total of 34.660962352921 HMNY
| stealth address | amount | amount idx | tag |
| 00: 66a044311022683cf7a020cc20cdebd31b40443ec84c960c2be809bcf3202a58 | 34.660962352921 | 9743 of 0 | <18> |
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": 7919,
"vin": [ {
"gen": {
"height": 7859
}
}
],
"vout": [ {
"amount": 34660962352921,
"target": {
"tagged_key": {
"key": "66a044311022683cf7a020cc20cdebd31b40443ec84c960c2be809bcf3202a58",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 135, 153, 183, 58, 215, 231, 253, 34, 75, 193, 152, 198, 117, 120, 193, 105, 131, 142, 51, 34, 0, 245, 194, 1, 184, 106, 241, 250, 3, 44, 83, 94, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}