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: 34f784d59fc8a797347d8eb1fb3616731fc5ae7e97b8df5a538dca4d0d1e73a4
Tx prefix hash: 102343cdde182c91df49d7daebd7460bcc5ca4bd0cf1204c5864353cfb35cf76
Tx public key: c192b56c714cf78cc20e70ab2f6b60a2c80fe6c52bb5c2b01a3e0d0cd1a65eea
| Timestamp: 1780078903 | Timestamp [UTC]: 2026-05-29 18:21:43 | Age [y:d:h:m:s]: 00:010:08:18:53 |
| Block: 4734 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3162 | RingCT/type: yes/0 |
| Extra: 01c192b56c714cf78cc20e70ab2f6b60a2c80fe6c52bb5c2b01a3e0d0cd1a65eea02090000000326697be300 | ||
1 output(s) for total of 34.868174913477 HMNY
| stealth address | amount | amount idx | tag |
| 00: b589a1f51abaed63032a04320cd3cffac0d78c538e0e8bfd2fe11ed51684f28a | 34.868174913477 | 5950 of 0 | <c3> |
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": 4794,
"vin": [ {
"gen": {
"height": 4734
}
}
],
"vout": [ {
"amount": 34868174913477,
"target": {
"tagged_key": {
"key": "b589a1f51abaed63032a04320cd3cffac0d78c538e0e8bfd2fe11ed51684f28a",
"view_tag": "c3"
}
}
}
],
"extra": [ 1, 193, 146, 181, 108, 113, 76, 247, 140, 194, 14, 112, 171, 47, 107, 96, 162, 200, 15, 230, 197, 43, 181, 194, 176, 26, 62, 13, 12, 209, 166, 94, 234, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}