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: e9405bd91710947add4bb0d3cc1dc70fa8ff4f6c3cbf9f84f214acf8ffd3fe1b
Tx prefix hash: 738b4f2b7e44acb623df0a58112d4bdf917f32140f277d598de82a00337de36f
Tx public key: 2c11ed4107352716ec59de7452fa24439a2902edb84937d09ac0b6b39035a307
| Timestamp: 1780986944 | Timestamp [UTC]: 2026-06-09 06:35:44 | Age [y:d:h:m:s]: 00:000:09:24:00 |
| Block: 8159 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 532 | RingCT/type: yes/0 |
| Extra: 012c11ed4107352716ec59de7452fa24439a2902edb84937d09ac0b6b39035a307020900000001e49593ff00 | ||
1 output(s) for total of 34.641134845501 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7c9684e14996f517f916959fff1b587bcf7d544e2d030513942935101e2d9b10 | 34.641134845501 | 10103 of 0 | <b5> |
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": 8219,
"vin": [ {
"gen": {
"height": 8159
}
}
],
"vout": [ {
"amount": 34641134845501,
"target": {
"tagged_key": {
"key": "7c9684e14996f517f916959fff1b587bcf7d544e2d030513942935101e2d9b10",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 44, 17, 237, 65, 7, 53, 39, 22, 236, 89, 222, 116, 82, 250, 36, 67, 154, 41, 2, 237, 184, 73, 55, 208, 154, 192, 182, 179, 144, 53, 163, 7, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}