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: 6529c34d3d2a45eb5d40a8d025e739545ff9ffec75ee97689e0990a031b64b83
Tx prefix hash: 79257d10f23ee3bfcc1d44c13af021aeca8b6e1c12938c7652b6007bf65b2bf9
Tx public key: 9fa6ba7c0dd271ed37e13699f661dbe6880f39bafcedc38d11406feb1f719bc0
| Timestamp: 1780990698 | Timestamp [UTC]: 2026-06-09 07:38:18 | Age [y:d:h:m:s]: 00:000:07:10:37 |
| Block: 8226 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 428 | RingCT/type: yes/0 |
| Extra: 019fa6ba7c0dd271ed37e13699f661dbe6880f39bafcedc38d11406feb1f719bc0020900000001e49593ff00 | ||
1 output(s) for total of 34.636708251809 HMNY
| stealth address | amount | amount idx | tag |
| 00: 09f33382f73e1ff8eac6bcdf61ec27cd4ca6dc80086f548bae6c84700f0fe4e2 | 34.636708251809 | 10182 of 0 | <10> |
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": 8286,
"vin": [ {
"gen": {
"height": 8226
}
}
],
"vout": [ {
"amount": 34636708251809,
"target": {
"tagged_key": {
"key": "09f33382f73e1ff8eac6bcdf61ec27cd4ca6dc80086f548bae6c84700f0fe4e2",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 159, 166, 186, 124, 13, 210, 113, 237, 55, 225, 54, 153, 246, 97, 219, 230, 136, 15, 57, 186, 252, 237, 195, 141, 17, 64, 111, 235, 31, 113, 155, 192, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}