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: 0e09b61ddd83674fb6c552ae2eabc7982aa4446b1ae723b86850db8e4e11a3aa
Tx prefix hash: 8f7387facf80ecb28e8f3e42da657af59e61026c42544a0e159fd0e0a5087803
Tx public key: 836d23ea132e537cf6d3467d3b46c69b5be383b7e514ece1a4a8bf14561b6c59
| Timestamp: 1779860794 | Timestamp [UTC]: 2026-05-27 05:46:34 | Age [y:d:h:m:s]: 00:013:11:22:29 |
| Block: 2681 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6052 | RingCT/type: yes/0 |
| Extra: 01836d23ea132e537cf6d3467d3b46c69b5be383b7e514ece1a4a8bf14561b6c5902090000000126697be300 | ||
1 output(s) for total of 35.004979054142 HMNY
| stealth address | amount | amount idx | tag |
| 00: c2151de84072871263d94ea6be53f1ab8a4acad186e7051a708f97d498b0a3e2 | 35.004979054142 | 3161 of 0 | <be> |
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": 2741,
"vin": [ {
"gen": {
"height": 2681
}
}
],
"vout": [ {
"amount": 35004979054142,
"target": {
"tagged_key": {
"key": "c2151de84072871263d94ea6be53f1ab8a4acad186e7051a708f97d498b0a3e2",
"view_tag": "be"
}
}
}
],
"extra": [ 1, 131, 109, 35, 234, 19, 46, 83, 124, 246, 211, 70, 125, 59, 70, 198, 155, 91, 227, 131, 183, 229, 20, 236, 225, 164, 168, 191, 20, 86, 27, 108, 89, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}