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: 3dd249907363a42b9a368cb45c0ff3ceb20c0110f0847ea0dbd72a5b15288389
Tx prefix hash: f342c4c425afdbcfe5ca63fe18fdadfea9adb12bb62ee6b13d68dfee1c90dbab
Tx public key: 616e7a99f3fd316a6f57cdd414400017853b30ba809641d64bef38881b4e3297
| Timestamp: 1780008029 | Timestamp [UTC]: 2026-05-28 22:40:29 | Age [y:d:h:m:s]: 00:011:04:00:07 |
| Block: 4087 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3810 | RingCT/type: yes/0 |
| Extra: 01616e7a99f3fd316a6f57cdd414400017853b30ba809641d64bef38881b4e329702090000000526697be300 | ||
1 output(s) for total of 34.913845546137 HMNY
| stealth address | amount | amount idx | tag |
| 00: e32d75dd2941179eb28405b1161f54bbfa67a8565d404f478a94896be2cfdb84 | 34.913845546137 | 5077 of 0 | <6e> |
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": 4147,
"vin": [ {
"gen": {
"height": 4087
}
}
],
"vout": [ {
"amount": 34913845546137,
"target": {
"tagged_key": {
"key": "e32d75dd2941179eb28405b1161f54bbfa67a8565d404f478a94896be2cfdb84",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 97, 110, 122, 153, 243, 253, 49, 106, 111, 87, 205, 212, 20, 64, 0, 23, 133, 59, 48, 186, 128, 150, 65, 214, 75, 239, 56, 136, 27, 78, 50, 151, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}