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: 2a7ad0de629cf2730a8ffbdef9d8ddfc199ff83fb4779c74846d527c81b2db10
Tx prefix hash: 8c0273fb3cfa8cee16d1c7f429bb56aa42e97dca3e37e2a6d2eb34c038da5b50
Tx public key: 46d46b7a7ddc42dd4662de65d83933ef7d193e776e63dde46c8bddc98987788c
| Timestamp: 1780691497 | Timestamp [UTC]: 2026-06-05 20:31:37 | Age [y:d:h:m:s]: 00:003:04:15:10 |
| Block: 5731 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2155 | RingCT/type: yes/0 |
| Extra: 0146d46b7a7ddc42dd4662de65d83933ef7d193e776e63dde46c8bddc98987788c020900000001e49593ff00 | ||
1 output(s) for total of 34.801931606828 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5e80c64d17cfd3a185b3739c70433cdaa6753c4de03b63a7ee18c006ae5e1b88 | 34.801931606828 | 7184 of 0 | <1e> |
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": 5791,
"vin": [ {
"gen": {
"height": 5731
}
}
],
"vout": [ {
"amount": 34801931606828,
"target": {
"tagged_key": {
"key": "5e80c64d17cfd3a185b3739c70433cdaa6753c4de03b63a7ee18c006ae5e1b88",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 70, 212, 107, 122, 125, 220, 66, 221, 70, 98, 222, 101, 216, 57, 51, 239, 125, 25, 62, 119, 110, 99, 221, 228, 108, 139, 221, 201, 137, 135, 120, 140, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}