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: 6d67d42bc5c911d0457593ffa36a0cb8e716c5bc9859e512a1a6c098e687c90a
Tx prefix hash: ac59320cf2946a2871f3bf715974f53fe46c7a2c2ca6ef5494c5cac93cf462c3
Tx public key: a4c6f9355cd7c77484a08393cc78b3539d5d730a71b7a1e26b9d8b64164d6483
| Timestamp: 1780701182 | Timestamp [UTC]: 2026-06-05 23:13:02 | Age [y:d:h:m:s]: 00:003:02:22:55 |
| Block: 6054 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1832 | RingCT/type: yes/0 |
| Extra: 01a4c6f9355cd7c77484a08393cc78b3539d5d730a71b7a1e26b9d8b64164d6483020900000001e49593ff00 | ||
1 output(s) for total of 34.780497637932 HMNY
| stealth address | amount | amount idx | tag |
| 00: a999b62603d6fcf56242203ef024e6da8f3176e833c56f19a87163612ca7bc9d | 34.780497637932 | 7523 of 0 | <b7> |
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": 6114,
"vin": [ {
"gen": {
"height": 6054
}
}
],
"vout": [ {
"amount": 34780497637932,
"target": {
"tagged_key": {
"key": "a999b62603d6fcf56242203ef024e6da8f3176e833c56f19a87163612ca7bc9d",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 164, 198, 249, 53, 92, 215, 199, 116, 132, 160, 131, 147, 204, 120, 179, 83, 157, 93, 115, 10, 113, 183, 161, 226, 107, 157, 139, 100, 22, 77, 100, 131, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}