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: 56c331a0065bb202b6a6f55e97f536a3ca7f579e617c03279a5bbebff70872b6
Tx prefix hash: 4cf650b2895dfae93487852d7073875ea106b8a16a73febb2448ebf8c12f2ea3
Tx public key: 41b1124c78b38f00a6e3d48651f85bdda2075ae23bd316d00e55c51e30e9f4a9
| Timestamp: 1781004197 | Timestamp [UTC]: 2026-06-09 11:23:17 | Age [y:d:h:m:s]: 00:000:04:36:27 |
| Block: 8503 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 188 | RingCT/type: yes/0 |
| Extra: 0141b1124c78b38f00a6e3d48651f85bdda2075ae23bd316d00e55c51e30e9f4a9020900000002e49593ff00 | ||
1 output(s) for total of 34.618413262692 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3003223ad489caadbb0930ebcbd23da15901df3990b2fea4dd202bbe30bad19d | 34.618413262692 | 10505 of 0 | <99> |
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": 8563,
"vin": [ {
"gen": {
"height": 8503
}
}
],
"vout": [ {
"amount": 34618413262692,
"target": {
"tagged_key": {
"key": "3003223ad489caadbb0930ebcbd23da15901df3990b2fea4dd202bbe30bad19d",
"view_tag": "99"
}
}
}
],
"extra": [ 1, 65, 177, 18, 76, 120, 179, 143, 0, 166, 227, 212, 134, 81, 248, 91, 221, 162, 7, 90, 226, 59, 211, 22, 208, 14, 85, 197, 30, 48, 233, 244, 169, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}