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: bf90cc0aa9852ba73830bde57adcd85f004a6bb187cdf67d6f2cda96b6a9b884
Tx prefix hash: a811a90a50fe76d93aa1735c0d0ffa05e48b909cba2df4ee9bf1f5ab81923150
Tx public key: 693510e362208a02d3ecb51f04ab45c549a07bfb8be2e38f26a98ccc2145e03c
| Timestamp: 1779997401 | Timestamp [UTC]: 2026-05-28 19:43:21 | Age [y:d:h:m:s]: 00:019:12:22:00 |
| Block: 4037 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4708 | RingCT/type: yes/0 |
| Extra: 01693510e362208a02d3ecb51f04ab45c549a07bfb8be2e38f26a98ccc2145e03c02090000000426697be300 | ||
1 output(s) for total of 34.914560302487 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30375796ba9add836bdbb110381d014463d2bb6e8feb4f2c0d81403b131ce4cd | 34.914560302487 | 4998 of 0 | <d1> |
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": 4097,
"vin": [ {
"gen": {
"height": 4037
}
}
],
"vout": [ {
"amount": 34914560302487,
"target": {
"tagged_key": {
"key": "30375796ba9add836bdbb110381d014463d2bb6e8feb4f2c0d81403b131ce4cd",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 105, 53, 16, 227, 98, 32, 138, 2, 211, 236, 181, 31, 4, 171, 69, 197, 73, 160, 123, 251, 139, 226, 227, 143, 38, 169, 140, 204, 33, 69, 224, 60, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}