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: a57d4b8fb213040d49503147c9a2a25e66882ad4276840b21b47efc9aa86d305
Tx prefix hash: 52456b54e2564ee2cda85a4e229717cc2f18a0b94230a3d5f2c7c05e702e6d94
Tx public key: 2cc74f14e347808f9cdb9ee863b2d90ff19adf2ddd871f20815ac60c1c52efac
| Timestamp: 1780692567 | Timestamp [UTC]: 2026-06-05 20:49:27 | Age [y:d:h:m:s]: 00:003:02:29:26 |
| Block: 5801 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2085 | RingCT/type: yes/0 |
| Extra: 012cc74f14e347808f9cdb9ee863b2d90ff19adf2ddd871f20815ac60c1c52efac020900000001e49593ff00 | ||
1 output(s) for total of 34.828731353408 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5db921058dc1648be6ab0e6e3cefde9d19adc3200dae5dd50f31028cc88bc2dd | 34.828731353408 | 7256 of 0 | <68> |
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": 5861,
"vin": [ {
"gen": {
"height": 5801
}
}
],
"vout": [ {
"amount": 34828731353408,
"target": {
"tagged_key": {
"key": "5db921058dc1648be6ab0e6e3cefde9d19adc3200dae5dd50f31028cc88bc2dd",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 44, 199, 79, 20, 227, 71, 128, 143, 156, 219, 158, 232, 99, 178, 217, 15, 241, 154, 223, 45, 221, 135, 31, 32, 129, 90, 198, 12, 28, 82, 239, 172, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}