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: 0158c411c3ccacb82641b1e08ad850df17f3dbdd5461d480034474c3822283ee
Tx prefix hash: e7bdddd433e4f86be59833b5df48d46907ff52e94257514e7bd90e5871c68746
Tx public key: ba9ccf23d47ce0976705823df6f19e482e3a8c28fd4f7ef9b612780d2e2bb5a9
| Timestamp: 1780070659 | Timestamp [UTC]: 2026-05-29 16:04:19 | Age [y:d:h:m:s]: 00:010:09:31:38 |
| Block: 4639 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3247 | RingCT/type: yes/0 |
| Extra: 01ba9ccf23d47ce0976705823df6f19e482e3a8c28fd4f7ef9b612780d2e2bb5a902090000000126697be300 | ||
1 output(s) for total of 34.874493539693 HMNY
| stealth address | amount | amount idx | tag |
| 00: cac2f4cb55d3605e6a0e2747a1cf6cdc96df7a698911134a2c0b48ff2eef9859 | 34.874493539693 | 5826 of 0 | <24> |
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": 4699,
"vin": [ {
"gen": {
"height": 4639
}
}
],
"vout": [ {
"amount": 34874493539693,
"target": {
"tagged_key": {
"key": "cac2f4cb55d3605e6a0e2747a1cf6cdc96df7a698911134a2c0b48ff2eef9859",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 186, 156, 207, 35, 212, 124, 224, 151, 103, 5, 130, 61, 246, 241, 158, 72, 46, 58, 140, 40, 253, 79, 126, 249, 182, 18, 120, 13, 46, 43, 181, 169, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}