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: 321650889e2dd6ef51959214c26b1c90ba8c78a0716ee66c4683a9baf9a82b0f
Tx prefix hash: de80da205ddb29307ac3aa765f69ac60bc1646da0b54b9f12c335d36e24b7124
Tx public key: 2c883b2209f1387a300c18ddaae888df8928a2cee10ff6f2809fdceafe4be119
| Timestamp: 1779793764 | Timestamp [UTC]: 2026-05-26 11:09:24 | Age [y:d:h:m:s]: 00:013:15:02:38 |
| Block: 2250 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5636 | RingCT/type: yes/0 |
| Extra: 012c883b2209f1387a300c18ddaae888df8928a2cee10ff6f2809fdceafe4be11902090000000226697be300 | ||
1 output(s) for total of 35.033767360181 HMNY
| stealth address | amount | amount idx | tag |
| 00: 57dc3ae06d2e75661c6e83728a3d5c1d2f6117984505a0415145dbb79dd29c05 | 35.033767360181 | 2612 of 0 | <b1> |
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": 2310,
"vin": [ {
"gen": {
"height": 2250
}
}
],
"vout": [ {
"amount": 35033767360181,
"target": {
"tagged_key": {
"key": "57dc3ae06d2e75661c6e83728a3d5c1d2f6117984505a0415145dbb79dd29c05",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 44, 136, 59, 34, 9, 241, 56, 122, 48, 12, 24, 221, 170, 232, 136, 223, 137, 40, 162, 206, 225, 15, 246, 242, 128, 159, 220, 234, 254, 75, 225, 25, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}