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: 3b01092d54c56e81aca48dbebddb583bc16fb12e3da3a1c5e2c54c06f2e59465
Tx prefix hash: d876e1ab642fbf866b6648027ef70507b7b36be5a452188cf27fad4f38f4ba58
Tx public key: be92c2fc861fc20e79d103f2c7f7a3ef843b4d87a44bbd561d63e33457952905
| Timestamp: 1779799396 | Timestamp [UTC]: 2026-05-26 12:43:16 | Age [y:d:h:m:s]: 00:013:10:35:37 |
| Block: 2292 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5594 | RingCT/type: yes/0 |
| Extra: 01be92c2fc861fc20e79d103f2c7f7a3ef843b4d87a44bbd561d63e3345795290502090000000226697be300 | ||
1 output(s) for total of 35.030960962366 HMNY
| stealth address | amount | amount idx | tag |
| 00: ad74105794772c07174f22e5417a0843860bcb3ff40d13aaf8005279926d4fb4 | 35.030960962366 | 2672 of 0 | <68> |
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": 2352,
"vin": [ {
"gen": {
"height": 2292
}
}
],
"vout": [ {
"amount": 35030960962366,
"target": {
"tagged_key": {
"key": "ad74105794772c07174f22e5417a0843860bcb3ff40d13aaf8005279926d4fb4",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 190, 146, 194, 252, 134, 31, 194, 14, 121, 209, 3, 242, 199, 247, 163, 239, 132, 59, 77, 135, 164, 75, 189, 86, 29, 99, 227, 52, 87, 149, 41, 5, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}