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: ad7c3dee801735bc95dd3b564beea2bb2d3fafc0ec9808b65265985f34d1fed0
Tx prefix hash: bd540bbbbdda650f5a80cb7189e1032936d20ddb8c9f61ebd66aaadfce374721
Tx public key: 3ae1b7238c19e295d5b889dc3f23fb36c8cdc7cd42ae44556caa3e155fa2efc9
| Timestamp: 1779949507 | Timestamp [UTC]: 2026-05-28 06:25:07 | Age [y:d:h:m:s]: 00:020:01:57:12 |
| Block: 3602 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5143 | RingCT/type: yes/0 |
| Extra: 013ae1b7238c19e295d5b889dc3f23fb36c8cdc7cd42ae44556caa3e155fa2efc902090000000326697be300 | ||
1 output(s) for total of 34.943540844896 HMNY
| stealth address | amount | amount idx | tag |
| 00: b7aa3e6e9038da837c8fccaca599d01603acc2e371f6366fde114dee6eefcf0f | 34.943540844896 | 4349 of 0 | <4b> |
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": 3662,
"vin": [ {
"gen": {
"height": 3602
}
}
],
"vout": [ {
"amount": 34943540844896,
"target": {
"tagged_key": {
"key": "b7aa3e6e9038da837c8fccaca599d01603acc2e371f6366fde114dee6eefcf0f",
"view_tag": "4b"
}
}
}
],
"extra": [ 1, 58, 225, 183, 35, 140, 25, 226, 149, 213, 184, 137, 220, 63, 35, 251, 54, 200, 205, 199, 205, 66, 174, 68, 85, 108, 170, 62, 21, 95, 162, 239, 201, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}