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: 17643265b0ab75cd49d17cac4ed280bd31b0c8f30d9971f45ba5a045e77e1809
Tx prefix hash: 12337263536a4b0d9e2be697ff69ac14ee70c46a175b98840eee0910ba8d898a
Tx public key: 93d769e2503938f1c6cc0da892c50b4476dc368ca3c0e3d91c7db313a80acee5
| Timestamp: 1779941221 | Timestamp [UTC]: 2026-05-28 04:07:01 | Age [y:d:h:m:s]: 00:011:21:28:56 |
| Block: 3500 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4386 | RingCT/type: yes/0 |
| Extra: 0193d769e2503938f1c6cc0da892c50b4476dc368ca3c0e3d91c7db313a80acee502090000000226697be300 | ||
1 output(s) for total of 34.950339763237 HMNY
| stealth address | amount | amount idx | tag |
| 00: 98a6adf99bb5d627744a1913f70cd71c28d1a01e424fc42e5026f030bdfc429f | 34.950339763237 | 4219 of 0 | <30> |
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": 3560,
"vin": [ {
"gen": {
"height": 3500
}
}
],
"vout": [ {
"amount": 34950339763237,
"target": {
"tagged_key": {
"key": "98a6adf99bb5d627744a1913f70cd71c28d1a01e424fc42e5026f030bdfc429f",
"view_tag": "30"
}
}
}
],
"extra": [ 1, 147, 215, 105, 226, 80, 57, 56, 241, 198, 204, 13, 168, 146, 197, 11, 68, 118, 220, 54, 140, 163, 192, 227, 217, 28, 125, 179, 19, 168, 10, 206, 229, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}