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: d98706f03906947e00849d508ab2191c1e843fdd1be55957dbb5a992822b6899
Tx prefix hash: 97509c5413c4d64f62f9b6665f7c504534eb2e8498b5ffba11bd8402e0252923
Tx public key: e4b6bd41b02a505b1571d6378bf30292bd9c564ec64659ba7764270ecea74d32
| Timestamp: 1780890066 | Timestamp [UTC]: 2026-06-08 03:41:06 | Age [y:d:h:m:s]: 00:000:21:05:41 |
| Block: 7713 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 173 | RingCT/type: yes/0 |
| Extra: 01e4b6bd41b02a505b1571d6378bf30292bd9c564ec64659ba7764270ecea74d320209000000014a728a4c00 | ||
1 output(s) for total of 34.674833844899 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2f40a291275fd29bc118002e26e3b2c3b07c9c37c9d874089948e3922b5e088b | 34.674833844899 | 9545 of 0 | <da> |
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": 7773,
"vin": [ {
"gen": {
"height": 7713
}
}
],
"vout": [ {
"amount": 34674833844899,
"target": {
"tagged_key": {
"key": "2f40a291275fd29bc118002e26e3b2c3b07c9c37c9d874089948e3922b5e088b",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 228, 182, 189, 65, 176, 42, 80, 91, 21, 113, 214, 55, 139, 243, 2, 146, 189, 156, 86, 78, 198, 70, 89, 186, 119, 100, 39, 14, 206, 167, 77, 50, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}