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: 743a5eb91fcf9993613b58fb7a6daf610dadfc4eab685bd46ec66e2262adf686
Tx prefix hash: 23f8a80fd0021fcda3c20a55bc46191a19f461583613ec2db53709b12a851c8f
Tx public key: f4c23c1a1478f66371ddb991bfbeb8f0bcdcd3cd05cc8cce6fd482650ecb9f5f
| Timestamp: 1780823917 | Timestamp [UTC]: 2026-06-07 09:18:37 | Age [y:d:h:m:s]: 00:001:11:53:30 |
| Block: 7227 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 659 | RingCT/type: yes/0 |
| Extra: 01f4c23c1a1478f66371ddb991bfbeb8f0bcdcd3cd05cc8cce6fd482650ecb9f5f020900000004e49593ff00 | ||
1 output(s) for total of 34.702769446537 HMNY
| stealth address | amount | amount idx | tag |
| 00: fed01b60ad6cff6a8c43b23441edf4331cad09b1a0130112ee1ba211479b9760 | 34.702769446537 | 8899 of 0 | <46> |
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": 7287,
"vin": [ {
"gen": {
"height": 7227
}
}
],
"vout": [ {
"amount": 34702769446537,
"target": {
"tagged_key": {
"key": "fed01b60ad6cff6a8c43b23441edf4331cad09b1a0130112ee1ba211479b9760",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 244, 194, 60, 26, 20, 120, 246, 99, 113, 221, 185, 145, 191, 190, 184, 240, 188, 220, 211, 205, 5, 204, 140, 206, 111, 212, 130, 101, 14, 203, 159, 95, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}