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: 385b0afd0e7f453cbbb1cd9e52a85b63d891d75bd1f434a29f209cd3d600502b
Tx prefix hash: d0355b7641a5fc6ae42fc2d5d709c2bdddb4440fa90fd6ee1e111ff1986e31ab
Tx public key: 4325939b370926eab89f7fd5d8e0981d85e41776ac86eb041b0afc4f747b26b9
| Timestamp: 1780902506 | Timestamp [UTC]: 2026-06-08 07:08:26 | Age [y:d:h:m:s]: 00:000:16:10:27 |
| Block: 7834 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 52 | RingCT/type: yes/0 |
| Extra: 014325939b370926eab89f7fd5d8e0981d85e41776ac86eb041b0afc4f747b26b90209000000024a728a4c00 | ||
1 output(s) for total of 34.662615157381 HMNY
| stealth address | amount | amount idx | tag |
| 00: fc1f032e850eef232ee18a9489be5d280cf74e175a7a252fa18a9f8731c0baff | 34.662615157381 | 9710 of 0 | <33> |
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": 7894,
"vin": [ {
"gen": {
"height": 7834
}
}
],
"vout": [ {
"amount": 34662615157381,
"target": {
"tagged_key": {
"key": "fc1f032e850eef232ee18a9489be5d280cf74e175a7a252fa18a9f8731c0baff",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 67, 37, 147, 155, 55, 9, 38, 234, 184, 159, 127, 213, 216, 224, 152, 29, 133, 228, 23, 118, 172, 134, 235, 4, 27, 10, 252, 79, 116, 123, 38, 185, 2, 9, 0, 0, 0, 2, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}