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: e71ae901677548ceb01cec0224603f26cfa981f3ada75daeeb00e6f1d283eb5e
Tx prefix hash: 5e16d7377c27d2590a9c4e8cc8505a567782f0008a42b2b713e9d9e24cd8ce1c
Tx public key: 87b50f065fa9b12a0661ccadd5b79ba26e044d7ebd8b3795b0098be9f686608b
| Timestamp: 1779944036 | Timestamp [UTC]: 2026-05-28 04:53:56 | Age [y:d:h:m:s]: 00:018:03:25:39 |
| Block: 3537 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5208 | RingCT/type: yes/0 |
| Extra: 0187b50f065fa9b12a0661ccadd5b79ba26e044d7ebd8b3795b0098be9f686608b02090000000126697be300 | ||
1 output(s) for total of 34.947873336054 HMNY
| stealth address | amount | amount idx | tag |
| 00: 09661a412b33216a51dc3db4cc659fae701f2c32060f7bd00178180450a1db7e | 34.947873336054 | 4265 of 0 | <79> |
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": 3597,
"vin": [ {
"gen": {
"height": 3537
}
}
],
"vout": [ {
"amount": 34947873336054,
"target": {
"tagged_key": {
"key": "09661a412b33216a51dc3db4cc659fae701f2c32060f7bd00178180450a1db7e",
"view_tag": "79"
}
}
}
],
"extra": [ 1, 135, 181, 15, 6, 95, 169, 177, 42, 6, 97, 204, 173, 213, 183, 155, 162, 110, 4, 77, 126, 189, 139, 55, 149, 176, 9, 139, 233, 246, 134, 96, 139, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}