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: 140ff3e04e3acbad1825e606447fe8864e2d21db36a6c279e82b25325830d33a
Tx prefix hash: 4beb1c59e56f72b304279954b84c40fc187fd40ebebd2378fce1d3d6e2b7c773
Tx public key: d5704ee6dee7e160aac62f5409d5b4b9129fd8a14da8cae9265d8c9b0643ab68
| Timestamp: 1779911215 | Timestamp [UTC]: 2026-05-27 19:46:55 | Age [y:d:h:m:s]: 00:012:05:49:02 |
| Block: 3248 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4638 | RingCT/type: yes/0 |
| Extra: 01d5704ee6dee7e160aac62f5409d5b4b9129fd8a14da8cae9265d8c9b0643ab6802090000000226697be300 | ||
1 output(s) for total of 34.967142762791 HMNY
| stealth address | amount | amount idx | tag |
| 00: e281c51f50d8d79b3e08ed7e3a5dd05ad51f5a6bd61ff6c54638990f1aaf4888 | 34.967142762791 | 3896 of 0 | <b5> |
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": 3308,
"vin": [ {
"gen": {
"height": 3248
}
}
],
"vout": [ {
"amount": 34967142762791,
"target": {
"tagged_key": {
"key": "e281c51f50d8d79b3e08ed7e3a5dd05ad51f5a6bd61ff6c54638990f1aaf4888",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 213, 112, 78, 230, 222, 231, 225, 96, 170, 198, 47, 84, 9, 213, 180, 185, 18, 159, 216, 161, 77, 168, 202, 233, 38, 93, 140, 155, 6, 67, 171, 104, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}