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: 5b5db9029a02c917856ff54bad1a694dc826a1c8fa7dbd75f1dd121f26717441
Tx prefix hash: ea6ccdfe1ca383239429e1cec86fe5b4f9797ec6908037eb2b99d26cf7e908b8
Tx public key: 882148a508f7851119b90ea83748ecc23521ea85ec50249bef89cefe21473dc0
| Timestamp: 1780692912 | Timestamp [UTC]: 2026-06-05 20:55:12 | Age [y:d:h:m:s]: 00:003:04:40:45 |
| Block: 5829 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2057 | RingCT/type: yes/0 |
| Extra: 01882148a508f7851119b90ea83748ecc23521ea85ec50249bef89cefe21473dc0020900000001e49593ff00 | ||
1 output(s) for total of 34.795427025729 HMNY
| stealth address | amount | amount idx | tag |
| 00: 541276a3235569e9c0ef3f30ef0ecdaf47e8467bc2140ea10e9d6fe0f8d56ad6 | 34.795427025729 | 7286 of 0 | <dc> |
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": 5889,
"vin": [ {
"gen": {
"height": 5829
}
}
],
"vout": [ {
"amount": 34795427025729,
"target": {
"tagged_key": {
"key": "541276a3235569e9c0ef3f30ef0ecdaf47e8467bc2140ea10e9d6fe0f8d56ad6",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 136, 33, 72, 165, 8, 247, 133, 17, 25, 185, 14, 168, 55, 72, 236, 194, 53, 33, 234, 133, 236, 80, 36, 155, 239, 137, 206, 254, 33, 71, 61, 192, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}