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: f370e25d772a10efd3d9c6b72fd827eab7c1c92b2d6178dcc70c6f8c76f9aeb0
Tx prefix hash: e999cf370bfad0a3d62e3fce5be3d249a3f3ac5dc0547f1ff70be90fcca1e822
Tx public key: 85fda7f3f59068b3491fded1a17ce5e44d4ba7c794a4c838ebaa6404f06781dd
| Timestamp: 1780086837 | Timestamp [UTC]: 2026-05-29 20:33:57 | Age [y:d:h:m:s]: 00:010:05:02:00 |
| Block: 4819 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3067 | RingCT/type: yes/0 |
| Extra: 0185fda7f3f59068b3491fded1a17ce5e44d4ba7c794a4c838ebaa6404f06781dd02090000000126697be300 | ||
1 output(s) for total of 34.862522376217 HMNY
| stealth address | amount | amount idx | tag |
| 00: 078f5fa38d74c7d24eb295ba4996eba075e1e738a2b879d10193bd0483fd679d | 34.862522376217 | 6063 of 0 | <b2> |
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": 4879,
"vin": [ {
"gen": {
"height": 4819
}
}
],
"vout": [ {
"amount": 34862522376217,
"target": {
"tagged_key": {
"key": "078f5fa38d74c7d24eb295ba4996eba075e1e738a2b879d10193bd0483fd679d",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 133, 253, 167, 243, 245, 144, 104, 179, 73, 31, 222, 209, 161, 124, 229, 228, 77, 75, 167, 199, 148, 164, 200, 56, 235, 170, 100, 4, 240, 103, 129, 221, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}