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: 04920361683b3e9c73f982207169e513a6f856465ab2caa5173a67e70b6ff66b
Tx prefix hash: 9b07edbe1d05cefc8100fb031ae8ba8dab76254dec8b12f0a4fb6ffc12aec6e3
Tx public key: ab74ea273f50ee9286aae70376bfe868a9cde6f3e86123d858295a5362f47a79
| Timestamp: 1780835998 | Timestamp [UTC]: 2026-06-07 12:39:58 | Age [y:d:h:m:s]: 00:005:22:22:18 |
| Block: 7407 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1338 | RingCT/type: yes/0 |
| Extra: 01ab74ea273f50ee9286aae70376bfe868a9cde6f3e86123d858295a5362f47a79020900000002e49593ff00 | ||
1 output(s) for total of 34.697498029787 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5ca672ee4bf94b1de00137bdb83040254fc355b3a29f67a56d65c15dd12010e7 | 34.697498029787 | 9119 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": 7467,
"vin": [ {
"gen": {
"height": 7407
}
}
],
"vout": [ {
"amount": 34697498029787,
"target": {
"tagged_key": {
"key": "5ca672ee4bf94b1de00137bdb83040254fc355b3a29f67a56d65c15dd12010e7",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 171, 116, 234, 39, 63, 80, 238, 146, 134, 170, 231, 3, 118, 191, 232, 104, 169, 205, 230, 243, 232, 97, 35, 216, 88, 41, 90, 83, 98, 244, 122, 121, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}