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: 13c9c945511576a2a24dcbf6f42cde523695806eda1ebcf023948dc91ce0ecfb
Tx prefix hash: 41d5cb873b442c37db7143c2421de254f38a0d44797fd7af97649d72c3c29844
Tx public key: aa904e1cae7d283cd53ae152e082f1a844d017770e1616685c95fbd5e4aa74b6
| Timestamp: 1779453621 | Timestamp [UTC]: 2026-05-22 12:40:21 | Age [y:d:h:m:s]: 00:017:12:55:36 |
| Block: 351 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7535 | RingCT/type: yes/0 |
| Extra: 01aa904e1cae7d283cd53ae152e082f1a844d017770e1616685c95fbd5e4aa74b602090000000193369e7d00 | ||
1 output(s) for total of 35.160891802416 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5346ee991df858028fc54b815236fdbe911d2ac9836029aa945d103901516f81 | 35.160891802416 | 347 of 0 | <86> |
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": 411,
"vin": [ {
"gen": {
"height": 351
}
}
],
"vout": [ {
"amount": 35160891802416,
"target": {
"tagged_key": {
"key": "5346ee991df858028fc54b815236fdbe911d2ac9836029aa945d103901516f81",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 170, 144, 78, 28, 174, 125, 40, 60, 213, 58, 225, 82, 224, 130, 241, 168, 68, 208, 23, 119, 14, 22, 22, 104, 92, 149, 251, 213, 228, 170, 116, 182, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}