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: 8c76ae69273b0784c0f64f775ac3a01a6558c65e5bf9bbcff4600a307011410e
Tx prefix hash: 1793550b6a816d516be8907ca5920d7dd6189a964fd17be12c2d2280688d0876
Tx public key: 7be84e9ca1a9a65812a6a844e5c7f3fbfbeac88cea35df02dde8bc1dc487a7f7
| Timestamp: 1780978630 | Timestamp [UTC]: 2026-06-09 04:17:10 | Age [y:d:h:m:s]: 00:000:10:31:45 |
| Block: 7983 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 656 | RingCT/type: yes/0 |
| Extra: 017be84e9ca1a9a65812a6a844e5c7f3fbfbeac88cea35df02dde8bc1dc487a7f7020900000001e49593ff00 | ||
1 output(s) for total of 34.652765607598 HMNY
| stealth address | amount | amount idx | tag |
| 00: d7428fea7626502114e1b622eade3b1d4655cc2597236eac9f58c30918271eb5 | 34.652765607598 | 9899 of 0 | <6a> |
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": 8043,
"vin": [ {
"gen": {
"height": 7983
}
}
],
"vout": [ {
"amount": 34652765607598,
"target": {
"tagged_key": {
"key": "d7428fea7626502114e1b622eade3b1d4655cc2597236eac9f58c30918271eb5",
"view_tag": "6a"
}
}
}
],
"extra": [ 1, 123, 232, 78, 156, 161, 169, 166, 88, 18, 166, 168, 68, 229, 199, 243, 251, 251, 234, 200, 140, 234, 53, 223, 2, 221, 232, 188, 29, 196, 135, 167, 247, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}