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: c7b28025f1ce061bf4b94c9a2abef2a5668f5af44f813b8f607b20d110295232
Tx prefix hash: bd596a9f29e932804a3af236b12174d0976c252f6faf8f8201a84115031b46c0
Tx public key: 274fe096742748b251e49f65b5fe6fcfcad141300c93b6c6f375cd56fb89a4ae
| Timestamp: 1780982604 | Timestamp [UTC]: 2026-06-09 05:23:24 | Age [y:d:h:m:s]: 00:000:07:14:21 |
| Block: 8066 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 507 | RingCT/type: yes/0 |
| Extra: 01274fe096742748b251e49f65b5fe6fcfcad141300c93b6c6f375cd56fb89a4ae020900000001e49593ff00 | ||
1 output(s) for total of 34.647280159455 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7a6a316b2711e411191651a695e8c2585b08ae28f0ee4bfe1d9f3a92e35a3b26 | 34.647280159455 | 9996 of 0 | <f5> |
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": 8126,
"vin": [ {
"gen": {
"height": 8066
}
}
],
"vout": [ {
"amount": 34647280159455,
"target": {
"tagged_key": {
"key": "7a6a316b2711e411191651a695e8c2585b08ae28f0ee4bfe1d9f3a92e35a3b26",
"view_tag": "f5"
}
}
}
],
"extra": [ 1, 39, 79, 224, 150, 116, 39, 72, 178, 81, 228, 159, 101, 181, 254, 111, 207, 202, 209, 65, 48, 12, 147, 182, 198, 243, 117, 205, 86, 251, 137, 164, 174, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}