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: 2c88ca094924ee3ab1152f8c36902359580835bfbe3ca64e71f40330e6f0955c
Tx prefix hash: b8805a4d808b7e4d13cba7cae884d717bdef4fa56e1242aab72ebb5d6e74d113
Tx public key: 161822bae51d851fcfc7fe6686c740526bc7c5d368985b414dd3c8e6bd1de586
| Timestamp: 1779438330 | Timestamp [UTC]: 2026-05-22 08:25:30 | Age [y:d:h:m:s]: 00:017:19:13:20 |
| Block: 186 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7762 | RingCT/type: yes/0 |
| Extra: 01161822bae51d851fcfc7fe6686c740526bc7c5d368985b414dd3c8e6bd1de5860209000000035cddc08000 | ||
1 output(s) for total of 35.171959127412 HMNY
| stealth address | amount | amount idx | tag |
| 00: 36d474640b8195a99d753ac3f827c0203aa377c1eb6bcf13799a6a00b76946aa | 35.171959127412 | 182 of 0 | <63> |
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": 246,
"vin": [ {
"gen": {
"height": 186
}
}
],
"vout": [ {
"amount": 35171959127412,
"target": {
"tagged_key": {
"key": "36d474640b8195a99d753ac3f827c0203aa377c1eb6bcf13799a6a00b76946aa",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 22, 24, 34, 186, 229, 29, 133, 31, 207, 199, 254, 102, 134, 199, 64, 82, 107, 199, 197, 211, 104, 152, 91, 65, 77, 211, 200, 230, 189, 29, 229, 134, 2, 9, 0, 0, 0, 3, 92, 221, 192, 128, 0
],
"rct_signatures": {
"type": 0
}
}