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: 46e13eabe99484ebb8336bd75b873eb21018db54c4b48dedd716c38667266667
Tx prefix hash: 2580f01882b0248b3d189f3e63594b489d2749a8db199f86d7e90623539ad157
Tx public key: c3cccb9f168a8f934557ca9c6bb4c0f2b038e68a5c9be0ba5e3a4aed240cd8d4
| Timestamp: 1780055081 | Timestamp [UTC]: 2026-05-29 11:44:41 | Age [y:d:h:m:s]: 00:010:13:51:16 |
| Block: 4442 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3444 | RingCT/type: yes/0 |
| Extra: 01c3cccb9f168a8f934557ca9c6bb4c0f2b038e68a5c9be0ba5e3a4aed240cd8d402090000000326697be300 | ||
1 output(s) for total of 34.887600024466 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4358801a969439524b395e1fff2878c2e338d03976ba4cad948f788ad276dabc | 34.887600024466 | 5560 of 0 | <e8> |
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": 4502,
"vin": [ {
"gen": {
"height": 4442
}
}
],
"vout": [ {
"amount": 34887600024466,
"target": {
"tagged_key": {
"key": "4358801a969439524b395e1fff2878c2e338d03976ba4cad948f788ad276dabc",
"view_tag": "e8"
}
}
}
],
"extra": [ 1, 195, 204, 203, 159, 22, 138, 143, 147, 69, 87, 202, 156, 107, 180, 192, 242, 176, 56, 230, 138, 92, 155, 224, 186, 94, 58, 74, 237, 36, 12, 216, 212, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}