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: cf314d01cb0d1d62251db39392631f3057adc687c4d5bf3a1e4fa46fe1f9e459
Tx prefix hash: 69384dae23ee7e01cbf63b1b4d7600c2aa7b1d82ad507d90bade72b808da6d39
Tx public key: b26f051bfb920aac724708dc8d377210ff535a076dd6947160d29c829469723a
| Timestamp: 1779802292 | Timestamp [UTC]: 2026-05-26 13:31:32 | Age [y:d:h:m:s]: 00:013:12:04:25 |
| Block: 2313 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5573 | RingCT/type: yes/0 |
| Extra: 01b26f051bfb920aac724708dc8d377210ff535a076dd6947160d29c829469723a02090000000126697be300 | ||
1 output(s) for total of 35.029557847763 HMNY
| stealth address | amount | amount idx | tag |
| 00: 77e5769b82b4330e34c24f66cd36960d3da8154bff1554c608118b667f381495 | 35.029557847763 | 2703 of 0 | <1d> |
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": 2373,
"vin": [ {
"gen": {
"height": 2313
}
}
],
"vout": [ {
"amount": 35029557847763,
"target": {
"tagged_key": {
"key": "77e5769b82b4330e34c24f66cd36960d3da8154bff1554c608118b667f381495",
"view_tag": "1d"
}
}
}
],
"extra": [ 1, 178, 111, 5, 27, 251, 146, 10, 172, 114, 71, 8, 220, 141, 55, 114, 16, 255, 83, 90, 7, 109, 214, 148, 113, 96, 210, 156, 130, 148, 105, 114, 58, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}