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: 48329cb7b99050da5595be14c1bdec0a487e0f0890240173877447fc536cc2df
Tx prefix hash: 1ddaf5bfcdd70b67e5e0aadf9241835266d403bbf2d49d819865e15f19beb24a
Tx public key: 891c925db8124ef5faa7c2699b65fe20c42438f839ab93e0d566d1c44f7f8c11
| Timestamp: 1779448292 | Timestamp [UTC]: 2026-05-22 11:11:32 | Age [y:d:h:m:s]: 00:017:14:24:25 |
| Block: 297 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7589 | RingCT/type: yes/0 |
| Extra: 01891c925db8124ef5faa7c2699b65fe20c42438f839ab93e0d566d1c44f7f8c110209000000014438f87f00 | ||
1 output(s) for total of 35.164513452637 HMNY
| stealth address | amount | amount idx | tag |
| 00: ea265e488416730f9394139f3f981820ce659b1c469afdc7845329f74319f4ac | 35.164513452637 | 293 of 0 | <6f> |
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": 357,
"vin": [ {
"gen": {
"height": 297
}
}
],
"vout": [ {
"amount": 35164513452637,
"target": {
"tagged_key": {
"key": "ea265e488416730f9394139f3f981820ce659b1c469afdc7845329f74319f4ac",
"view_tag": "6f"
}
}
}
],
"extra": [ 1, 137, 28, 146, 93, 184, 18, 78, 245, 250, 167, 194, 105, 155, 101, 254, 32, 196, 36, 56, 248, 57, 171, 147, 224, 213, 102, 209, 196, 79, 127, 140, 17, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}