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: 89e8265d97f9cc6d2d5e5836e6c5f95d5ca327d14b32d36d3c5e496afd8e155d
Tx prefix hash: d8fe8c9ed25f739159977821c2b674b4fe66674271da785d281e3ad951dd0005
Tx public key: 97c39e9abec5af4e358678bc86df215370bca8658a3fbf7776b25ec7d8739a0a
| Timestamp: 1780693806 | Timestamp [UTC]: 2026-06-05 21:10:06 | Age [y:d:h:m:s]: 00:003:04:25:51 |
| Block: 5899 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1987 | RingCT/type: yes/0 |
| Extra: 0197c39e9abec5af4e358678bc86df215370bca8658a3fbf7776b25ec7d8739a0a020900000001e49593ff00 | ||
1 output(s) for total of 34.790781640707 HMNY
| stealth address | amount | amount idx | tag |
| 00: 903e8397f414933b0ccbb4f68e8b1265a38246479137309170bb06beb6525231 | 34.790781640707 | 7360 of 0 | <57> |
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": 5959,
"vin": [ {
"gen": {
"height": 5899
}
}
],
"vout": [ {
"amount": 34790781640707,
"target": {
"tagged_key": {
"key": "903e8397f414933b0ccbb4f68e8b1265a38246479137309170bb06beb6525231",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 151, 195, 158, 154, 190, 197, 175, 78, 53, 134, 120, 188, 134, 223, 33, 83, 112, 188, 168, 101, 138, 63, 191, 119, 118, 178, 94, 199, 216, 115, 154, 10, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}