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: fd2cd0c3117c166f09fb2c50bd9429ca0af29957de3b1e6f00755b4d1326fd45
Tx prefix hash: 301f4c0a5fbd0d2d737a84a8de6175c3b479eb2f654b101b59c52f2e0af078de
Tx public key: 69abed3ee81e634d903b13753767639bdbc5ed41ec043b8885def594833de379
| Timestamp: 1780693741 | Timestamp [UTC]: 2026-06-05 21:09:01 | Age [y:d:h:m:s]: 00:003:04:26:56 |
| Block: 5893 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1993 | RingCT/type: yes/0 |
| Extra: 0169abed3ee81e634d903b13753767639bdbc5ed41ec043b8885def594833de379020900000001e49593ff00 | ||
1 output(s) for total of 34.791179792264 HMNY
| stealth address | amount | amount idx | tag |
| 00: c9c59074dc8d570807b018806f78b0dcf89d2a93a188e0817ab089f70be2d277 | 34.791179792264 | 7352 of 0 | <8e> |
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": 5953,
"vin": [ {
"gen": {
"height": 5893
}
}
],
"vout": [ {
"amount": 34791179792264,
"target": {
"tagged_key": {
"key": "c9c59074dc8d570807b018806f78b0dcf89d2a93a188e0817ab089f70be2d277",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 105, 171, 237, 62, 232, 30, 99, 77, 144, 59, 19, 117, 55, 103, 99, 155, 219, 197, 237, 65, 236, 4, 59, 136, 133, 222, 245, 148, 131, 61, 227, 121, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}