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: ac26977addb6f0983bdc8055d0d9f00d096bcc24fdc3fce127785ae2cb0a15a8
Tx prefix hash: 2652750f059a1fbb21ba027fe2992443f1f3402a06abe30f4464bdaae1d5a73d
Tx public key: 8d47d24d8ef4ae44ee6ff4a8d0e0b423e2b3c998fddb6819c6a3e05e2d6eaba9
| Timestamp: 1779948400 | Timestamp [UTC]: 2026-05-28 06:06:40 | Age [y:d:h:m:s]: 00:011:18:40:07 |
| Block: 3588 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4298 | RingCT/type: yes/0 |
| Extra: 018d47d24d8ef4ae44ee6ff4a8d0e0b423e2b3c998fddb6819c6a3e05e2d6eaba902090000000226697be300 | ||
1 output(s) for total of 34.944473951452 HMNY
| stealth address | amount | amount idx | tag |
| 00: 90d4833746484fceb0e5ae477901bfea06aba5c116fd04c8d8003bd7f8f36c90 | 34.944473951452 | 4331 of 0 | <fa> |
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": 3648,
"vin": [ {
"gen": {
"height": 3588
}
}
],
"vout": [ {
"amount": 34944473951452,
"target": {
"tagged_key": {
"key": "90d4833746484fceb0e5ae477901bfea06aba5c116fd04c8d8003bd7f8f36c90",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 141, 71, 210, 77, 142, 244, 174, 68, 238, 111, 244, 168, 208, 224, 180, 35, 226, 179, 201, 152, 253, 219, 104, 25, 198, 163, 224, 94, 45, 110, 171, 169, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}