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: b5ab939e7308d4e27c8ce470fd6611bf00289314781764a4d1a461d80678f40f
Tx prefix hash: 96f1e106efb78e15687ff0209a326d0ef1f434c46e05e09767a6afd49ce85f49
Tx public key: 05fa735b1184cc730c3b4d8881885e001d43b4c4663d44c8ab41e2129a4d37ac
| Timestamp: 1780735330 | Timestamp [UTC]: 2026-06-06 08:42:10 | Age [y:d:h:m:s]: 00:002:16:53:47 |
| Block: 6361 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1525 | RingCT/type: yes/0 |
| Extra: 0105fa735b1184cc730c3b4d8881885e001d43b4c4663d44c8ab41e2129a4d37ac020900000004e49593ff00 | ||
1 output(s) for total of 34.760137649926 HMNY
| stealth address | amount | amount idx | tag |
| 00: 55b3bf8ba588f058d65cb98bb25fcb51170dc988f8a1397341806c9c9cb5fb10 | 34.760137649926 | 7850 of 0 | <51> |
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": 6421,
"vin": [ {
"gen": {
"height": 6361
}
}
],
"vout": [ {
"amount": 34760137649926,
"target": {
"tagged_key": {
"key": "55b3bf8ba588f058d65cb98bb25fcb51170dc988f8a1397341806c9c9cb5fb10",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 5, 250, 115, 91, 17, 132, 204, 115, 12, 59, 77, 136, 129, 136, 94, 0, 29, 67, 180, 196, 102, 61, 68, 200, 171, 65, 226, 18, 154, 77, 55, 172, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}