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: 152a344b7de646250a0cc6f9df6e427958a0271ac38931ad39dd4c2ddd6575de
Tx prefix hash: ddb8efd000209772b75eb5fd34ed342e53d69632059d41fb367d421edf2bf0de
Tx public key: 6a80a4cbeb7e79badf881c3d93f21ebf05eb9de687257939043ef740d272d60e
| Timestamp: 1781001016 | Timestamp [UTC]: 2026-06-09 10:30:16 | Age [y:d:h:m:s]: 00:008:01:05:49 |
| Block: 8450 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 295 | RingCT/type: yes/0 |
| Extra: 016a80a4cbeb7e79badf881c3d93f21ebf05eb9de687257939043ef740d272d60e020900000001e49593ff00 | ||
1 output(s) for total of 34.621913000230 HMNY
| stealth address | amount | amount idx | tag |
| 00: 97acdc23b9fb71e3ddf3d8bfc8aa80b3929df6c2bdb795b5f32eb7e65ac198ce | 34.621913000230 | 10442 of 0 | <e3> |
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": 8510,
"vin": [ {
"gen": {
"height": 8450
}
}
],
"vout": [ {
"amount": 34621913000230,
"target": {
"tagged_key": {
"key": "97acdc23b9fb71e3ddf3d8bfc8aa80b3929df6c2bdb795b5f32eb7e65ac198ce",
"view_tag": "e3"
}
}
}
],
"extra": [ 1, 106, 128, 164, 203, 235, 126, 121, 186, 223, 136, 28, 61, 147, 242, 30, 191, 5, 235, 157, 230, 135, 37, 121, 57, 4, 62, 247, 64, 210, 114, 214, 14, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}