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: a76f39714aebb42acc280675ce4a9112ebf9f932e004f9fbe8f90728f4304eb7
Tx prefix hash: 97ce02d75b1139cb1d7a740072eab81dc68b5a1ae709de4c259c64e521ccc214
Tx public key: 066beba3e0c75d27f7adf77ce891f964a8b0a72752c5b5e195ed8195aadd32cb
| Timestamp: 1779900968 | Timestamp [UTC]: 2026-05-27 16:56:08 | Age [y:d:h:m:s]: 00:012:08:39:49 |
| Block: 3142 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4744 | RingCT/type: yes/0 |
| Extra: 01066beba3e0c75d27f7adf77ce891f964a8b0a72752c5b5e195ed8195aadd32cb02090000000126697be300 | ||
1 output(s) for total of 34.974213104633 HMNY
| stealth address | amount | amount idx | tag |
| 00: cf307918cd4f79e8747ddc3ea5d0d8e60a8627cfe40cba26430ca61a0dd4df09 | 34.974213104633 | 3756 of 0 | <09> |
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": 3202,
"vin": [ {
"gen": {
"height": 3142
}
}
],
"vout": [ {
"amount": 34974213104633,
"target": {
"tagged_key": {
"key": "cf307918cd4f79e8747ddc3ea5d0d8e60a8627cfe40cba26430ca61a0dd4df09",
"view_tag": "09"
}
}
}
],
"extra": [ 1, 6, 107, 235, 163, 224, 199, 93, 39, 247, 173, 247, 124, 232, 145, 249, 100, 168, 176, 167, 39, 82, 197, 181, 225, 149, 237, 129, 149, 170, 221, 50, 203, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}