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: 1c6c46c6775a6f33b736365c7338ae4d9c27822a8999022c47664f929ef39c94
Tx prefix hash: 75f5fa02900aa271d7501f6c7d8096de9f5628bce3fd7fda65539723cab2ac6b
Tx public key: a8fde1ac55ec3ea516423c9778c3a95cc16d9b27bc70fa5afecd81dfbdcfc414
| Timestamp: 1779641680 | Timestamp [UTC]: 2026-05-24 16:54:40 | Age [y:d:h:m:s]: 00:015:06:24:13 |
| Block: 1355 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6531 | RingCT/type: yes/0 |
| Extra: 01a8fde1ac55ec3ea516423c9778c3a95cc16d9b27bc70fa5afecd81dfbdcfc414020900000001ba6d17be00 | ||
1 output(s) for total of 35.093623831940 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0e11fa28eadc47af91997744a00bb99e0fd804373e90746ad8b6bf360bff7c50 | 35.093623831940 | 1505 of 0 | <84> |
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": 1415,
"vin": [ {
"gen": {
"height": 1355
}
}
],
"vout": [ {
"amount": 35093623831940,
"target": {
"tagged_key": {
"key": "0e11fa28eadc47af91997744a00bb99e0fd804373e90746ad8b6bf360bff7c50",
"view_tag": "84"
}
}
}
],
"extra": [ 1, 168, 253, 225, 172, 85, 236, 62, 165, 22, 66, 60, 151, 120, 195, 169, 92, 193, 109, 155, 39, 188, 112, 250, 90, 254, 205, 129, 223, 189, 207, 196, 20, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}