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: 0ac7861216d620e032600a759c7dc894b43b21e6f44437c4a89dfe57f0358c4a
Tx prefix hash: 65c5ae17c821386c8754854cf2a55930038cc87d27f5e9b7b21bcbe2ee3a97d5
Tx public key: 9b86920e95dfb4f1d33db3e8c46229a83054493026e2dd09dca0b0cee9b66761
| Timestamp: 1779857689 | Timestamp [UTC]: 2026-05-27 04:54:49 | Age [y:d:h:m:s]: 00:012:20:41:08 |
| Block: 2636 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5250 | RingCT/type: yes/0 |
| Extra: 019b86920e95dfb4f1d33db3e8c46229a83054493026e2dd09dca0b0cee9b6676102090000000126697be300 | ||
1 output(s) for total of 35.007983687403 HMNY
| stealth address | amount | amount idx | tag |
| 00: 14ea54dd091cfcfc719aed7f43521700ed412741fd96a8a39fb6c9c8ff9afb5a | 35.007983687403 | 3106 of 0 | <10> |
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": 2696,
"vin": [ {
"gen": {
"height": 2636
}
}
],
"vout": [ {
"amount": 35007983687403,
"target": {
"tagged_key": {
"key": "14ea54dd091cfcfc719aed7f43521700ed412741fd96a8a39fb6c9c8ff9afb5a",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 155, 134, 146, 14, 149, 223, 180, 241, 211, 61, 179, 232, 196, 98, 41, 168, 48, 84, 73, 48, 38, 226, 221, 9, 220, 160, 176, 206, 233, 182, 103, 97, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}