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: 49a9382c42d9b41ba6fd7269df81adcab749b0d0b1a6bb5648d8921c9b9d53da
Tx prefix hash: 9e5476da1b324c8a8519faf5166295cbd058f0a99f4251dd04d6d49232460879
Tx public key: 1b56a5b0eb024258f059022466a561f4f2d9fdbbb8237e0cfcdb0d1ff9bbf14a
| Timestamp: 1781015970 | Timestamp [UTC]: 2026-06-09 14:39:30 | Age [y:d:h:m:s]: 00:007:17:25:51 |
| Block: 8634 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 111 | RingCT/type: yes/0 |
| Extra: 011b56a5b0eb024258f059022466a561f4f2d9fdbbb8237e0cfcdb0d1ff9bbf14a020900000002e49593ff00 | ||
1 output(s) for total of 34.617986885792 HMNY
| stealth address | amount | amount idx | tag |
| 00: 56883ce0bdecc5ff6654edf0d9f18cd4c799a74ab616973319d2fa9ddb06346f | 34.617986885792 | 10672 of 0 | <b7> |
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": 8694,
"vin": [ {
"gen": {
"height": 8634
}
}
],
"vout": [ {
"amount": 34617986885792,
"target": {
"tagged_key": {
"key": "56883ce0bdecc5ff6654edf0d9f18cd4c799a74ab616973319d2fa9ddb06346f",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 27, 86, 165, 176, 235, 2, 66, 88, 240, 89, 2, 36, 102, 165, 97, 244, 242, 217, 253, 187, 184, 35, 126, 12, 252, 219, 13, 31, 249, 187, 241, 74, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}