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: befaf510da73dc0d051cc05e5c411e84e0708c3f6fb2985b05645df5426aa638
Tx prefix hash: 56c41b80ad3ffedc9f341459cad9f3c3eb891d600e6daf4d208c1a6cb6f45f5d
Tx public key: 9533f645d9ba2fffef226bdc2911a4a0b16e8ffaf6baf6840473383c72beca6e
| Timestamp: 1780988464 | Timestamp [UTC]: 2026-06-09 07:01:04 | Age [y:d:h:m:s]: 00:000:06:36:32 |
| Block: 8184 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 417 | RingCT/type: yes/0 |
| Extra: 019533f645d9ba2fffef226bdc2911a4a0b16e8ffaf6baf6840473383c72beca6e020900000003e49593ff00 | ||
1 output(s) for total of 34.647716265278 HMNY
| stealth address | amount | amount idx | tag |
| 00: e23c85750af2a0f5af16eea0b9e00ccae650a369fe3d0ac8704d3db1aea2278f | 34.647716265278 | 10132 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": 8244,
"vin": [ {
"gen": {
"height": 8184
}
}
],
"vout": [ {
"amount": 34647716265278,
"target": {
"tagged_key": {
"key": "e23c85750af2a0f5af16eea0b9e00ccae650a369fe3d0ac8704d3db1aea2278f",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 149, 51, 246, 69, 217, 186, 47, 255, 239, 34, 107, 220, 41, 17, 164, 160, 177, 110, 143, 250, 246, 186, 246, 132, 4, 115, 56, 60, 114, 190, 202, 110, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}