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: 2d46c2c55646f87c938f26b4bda7c2803153cdb8f8269fe217ba67381d9523ac
Tx prefix hash: e9d95ed2dfb8f07cca5553b486b1537c272768e0dbda356da3b9383586cc7215
Tx public key: 7688e0dc6d7c36b91d7a4c3406560431ee641d7ab3853d0ac6b76d3e0563af6d
| Timestamp: 1779640193 | Timestamp [UTC]: 2026-05-24 16:29:53 | Age [y:d:h:m:s]: 00:015:12:03:09 |
| Block: 1281 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6748 | RingCT/type: yes/0 |
| Extra: 017688e0dc6d7c36b91d7a4c3406560431ee641d7ab3853d0ac6b76d3e0563af6d020900000001ba6d17be00 | ||
1 output(s) for total of 35.098577433623 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5ebf7f28f7ba43566409f5abf0d1a432469a2e745e7b224029c8ab17f52ee10d | 35.098577433623 | 1429 of 0 | <dc> |
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": 1341,
"vin": [ {
"gen": {
"height": 1281
}
}
],
"vout": [ {
"amount": 35098577433623,
"target": {
"tagged_key": {
"key": "5ebf7f28f7ba43566409f5abf0d1a432469a2e745e7b224029c8ab17f52ee10d",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 118, 136, 224, 220, 109, 124, 54, 185, 29, 122, 76, 52, 6, 86, 4, 49, 238, 100, 29, 122, 179, 133, 61, 10, 198, 183, 109, 62, 5, 99, 175, 109, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}