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: 11a51ddae3de538aa9f57d50f6d2ac7e63634fd7d2a8ce686c1776bf5b20bf83
Tx prefix hash: 694cf8c7e8637e203492d583b0d23769695866da88217b48074e6a53801a833f
Tx public key: 6e3a0eab5f700b524a7a426513bfe953f58d0d70b42946b0b01e35a7cd6fa78a
| Timestamp: 1780059838 | Timestamp [UTC]: 2026-05-29 13:03:58 | Age [y:d:h:m:s]: 00:010:13:36:38 |
| Block: 4504 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3392 | RingCT/type: yes/0 |
| Extra: 016e3a0eab5f700b524a7a426513bfe953f58d0d70b42946b0b01e35a7cd6fa78a02090000000526697be300 | ||
1 output(s) for total of 34.883474609858 HMNY
| stealth address | amount | amount idx | tag |
| 00: b9f50f0a786680d4478de32eaeeeffe23c0f92de03e4095b94aa6876bebca412 | 34.883474609858 | 5646 of 0 | <93> |
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": 4564,
"vin": [ {
"gen": {
"height": 4504
}
}
],
"vout": [ {
"amount": 34883474609858,
"target": {
"tagged_key": {
"key": "b9f50f0a786680d4478de32eaeeeffe23c0f92de03e4095b94aa6876bebca412",
"view_tag": "93"
}
}
}
],
"extra": [ 1, 110, 58, 14, 171, 95, 112, 11, 82, 74, 122, 66, 101, 19, 191, 233, 83, 245, 141, 13, 112, 180, 41, 70, 176, 176, 30, 53, 167, 205, 111, 167, 138, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}