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: 1e09d22f7a9b7afaed303d01e26df83a2b7575af4ef06b2321abf09f33a71b10
Tx prefix hash: cc9bbde6927e9ecc8faf2c4a3f61015193e537d701b5d70a1f44000030ab6fb3
Tx public key: 10887d9c1fac0071c7a7b47667f7443c69d53d7f7a0f654bd558c24680b7c5c5
| Timestamp: 1779439108 | Timestamp [UTC]: 2026-05-22 08:38:28 | Age [y:d:h:m:s]: 00:017:16:57:29 |
| Block: 200 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7686 | RingCT/type: yes/0 |
| Extra: 0110887d9c1fac0071c7a7b47667f7443c69d53d7f7a0f654bd558c24680b7c5c5020900000003f2c813e500 | ||
1 output(s) for total of 35.171019946421 HMNY
| stealth address | amount | amount idx | tag |
| 00: ac05bae0ab8a55edf9e0ad67954a2aad24926aca226dba34846be05701565456 | 35.171019946421 | 196 of 0 | <c8> |
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": 260,
"vin": [ {
"gen": {
"height": 200
}
}
],
"vout": [ {
"amount": 35171019946421,
"target": {
"tagged_key": {
"key": "ac05bae0ab8a55edf9e0ad67954a2aad24926aca226dba34846be05701565456",
"view_tag": "c8"
}
}
}
],
"extra": [ 1, 16, 136, 125, 156, 31, 172, 0, 113, 199, 167, 180, 118, 103, 247, 68, 60, 105, 213, 61, 127, 122, 15, 101, 75, 213, 88, 194, 70, 128, 183, 197, 197, 2, 9, 0, 0, 0, 3, 242, 200, 19, 229, 0
],
"rct_signatures": {
"type": 0
}
}