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: a9f086e7bfdf6d5f0bfcd742ca313785e6cc8d5bfef6e9a0ed97a15ed7764b23
Tx prefix hash: 4f0e077dd65971b2d57e7816d31a9dacf1241775f4585c8029c426216e15987c
Tx public key: f3f3825d2c1c4020b520c1f9452ec3b40ee3f7949047173d74d0f4fa18764c22
| Timestamp: 1780974174 | Timestamp [UTC]: 2026-06-09 03:02:54 | Age [y:d:h:m:s]: 00:000:09:30:33 |
| Block: 7915 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 655 | RingCT/type: yes/0 |
| Extra: 01f3f3825d2c1c4020b520c1f9452ec3b40ee3f7949047173d74d0f4fa18764c22020900000002e49593ff00 | ||
1 output(s) for total of 34.657260356909 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c9942b5efd08a85382975be618c653b745c3c8b81693b0462aa0b921e3a9967 | 34.657260356909 | 9815 of 0 | <e9> |
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": 7975,
"vin": [ {
"gen": {
"height": 7915
}
}
],
"vout": [ {
"amount": 34657260356909,
"target": {
"tagged_key": {
"key": "2c9942b5efd08a85382975be618c653b745c3c8b81693b0462aa0b921e3a9967",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 243, 243, 130, 93, 44, 28, 64, 32, 181, 32, 193, 249, 69, 46, 195, 180, 14, 227, 247, 148, 144, 71, 23, 61, 116, 208, 244, 250, 24, 118, 76, 34, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}