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: 360633718e0bd196d5b380102a36f38a99a2b697e912493fe9df370f6ef77cef
Tx prefix hash: f0db49bb03a497addc74fb46df6587c3f9b168f1ca59e9e620074a9af7977017
Tx public key: 10ffa34eb042a75d31e47a4be811b97960d37e6c79cf1c0f805b34d04020d477
| Timestamp: 1779722635 | Timestamp [UTC]: 2026-05-25 15:23:55 | Age [y:d:h:m:s]: 00:014:10:12:02 |
| Block: 1783 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6103 | RingCT/type: yes/0 |
| Extra: 0110ffa34eb042a75d31e47a4be811b97960d37e6c79cf1c0f805b34d04020d477020900000003ba6d17be00 | ||
1 output(s) for total of 35.064986983111 HMNY
| stealth address | amount | amount idx | tag |
| 00: 825836bb5283da446c3ae17ca2a8381a2a462fc89a38cf37064da24c48f250e3 | 35.064986983111 | 1970 of 0 | <24> |
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": 1843,
"vin": [ {
"gen": {
"height": 1783
}
}
],
"vout": [ {
"amount": 35064986983111,
"target": {
"tagged_key": {
"key": "825836bb5283da446c3ae17ca2a8381a2a462fc89a38cf37064da24c48f250e3",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 16, 255, 163, 78, 176, 66, 167, 93, 49, 228, 122, 75, 232, 17, 185, 121, 96, 211, 126, 108, 121, 207, 28, 15, 128, 91, 52, 208, 64, 32, 212, 119, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}