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: 03bc8cacad2fd744b751732d7b9fc8b9bbee3ecb84d06739caad4d1c6e28a4bb
Tx prefix hash: cec7b3aab386c184a2fd042dd8014a86de9444a77043e10b1b7a1df23f6faa2a
Tx public key: 69e64bc935ddee63d8aa8cb4c93970baf96a76b69b27a8d4e4bb085edd6a44df
| Timestamp: 1780744406 | Timestamp [UTC]: 2026-06-06 11:13:26 | Age [y:d:h:m:s]: 00:006:23:48:50 |
| Block: 6444 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2301 | RingCT/type: yes/0 |
| Extra: 0169e64bc935ddee63d8aa8cb4c93970baf96a76b69b27a8d4e4bb085edd6a44df020900000001e49593ff00 | ||
1 output(s) for total of 34.754635205051 HMNY
| stealth address | amount | amount idx | tag |
| 00: 09b662ac8fc86f57cefa96fdfab86ec400372c2eb525114f022377913f4f045e | 34.754635205051 | 7937 of 0 | <bc> |
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": 6504,
"vin": [ {
"gen": {
"height": 6444
}
}
],
"vout": [ {
"amount": 34754635205051,
"target": {
"tagged_key": {
"key": "09b662ac8fc86f57cefa96fdfab86ec400372c2eb525114f022377913f4f045e",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 105, 230, 75, 201, 53, 221, 238, 99, 216, 170, 140, 180, 201, 57, 112, 186, 249, 106, 118, 182, 155, 39, 168, 212, 228, 187, 8, 94, 221, 106, 68, 223, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}