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: d34d87ebea9af94ea890f902b9fc0bfb62d3caddb8bd3a4deaa45279b4274fd9
Tx prefix hash: 06aa30457370462e1d06840db69e04de34cf6ea924ae1d0dc6b41ab23ed7df8f
Tx public key: f3593c5db356f3a9b2f53a213986830f04fc793b109f2f86f08e814b132991c0
| Timestamp: 1779433801 | Timestamp [UTC]: 2026-05-22 07:10:01 | Age [y:d:h:m:s]: 00:017:18:25:56 |
| Block: 65 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0908 kB |
| Tx version: 2 | No of confirmations: 7821 | RingCT/type: yes/0 |
| Extra: 01f3593c5db356f3a9b2f53a213986830f04fc793b109f2f86f08e814b132991c0020900000001a662ed0300 | ||
1 output(s) for total of 35.180077379687 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2211e7acd17f9badf6c0b8625bf109df7975f1c9dc56cf18c3762918ac23bdc1 | 35.180077379687 | 61 of 0 | <43> |
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": 125,
"vin": [ {
"gen": {
"height": 65
}
}
],
"vout": [ {
"amount": 35180077379687,
"target": {
"tagged_key": {
"key": "2211e7acd17f9badf6c0b8625bf109df7975f1c9dc56cf18c3762918ac23bdc1",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 243, 89, 60, 93, 179, 86, 243, 169, 178, 245, 58, 33, 57, 134, 131, 15, 4, 252, 121, 59, 16, 159, 47, 134, 240, 142, 129, 75, 19, 41, 145, 192, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}