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: bc16da6068d3b48817f7dd2c428f80f6449ea9fb20d8d895dcb2ba46373fb5ba
Tx prefix hash: 5b6425c5e584d08d17bcb7776f1349d675a4b3e31d1aa3ed130f021e99a876b7
Tx public key: 10c575f84848c661efe6fc3c0d6aaa86492213f550750c14aff6a2e070bd3c1e
| Timestamp: 1779640455 | Timestamp [UTC]: 2026-05-24 16:34:15 | Age [y:d:h:m:s]: 00:015:09:01:42 |
| Block: 1295 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6591 | RingCT/type: yes/0 |
| Extra: 0110c575f84848c661efe6fc3c0d6aaa86492213f550750c14aff6a2e070bd3c1e020900000001ba6d17be00 | ||
1 output(s) for total of 35.097640212111 HMNY
| stealth address | amount | amount idx | tag |
| 00: cdc0dd98abd9b422a2f6b5eff4c8a494c62921651e4898cd8bf09422b474a025 | 35.097640212111 | 1443 of 0 | <66> |
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": 1355,
"vin": [ {
"gen": {
"height": 1295
}
}
],
"vout": [ {
"amount": 35097640212111,
"target": {
"tagged_key": {
"key": "cdc0dd98abd9b422a2f6b5eff4c8a494c62921651e4898cd8bf09422b474a025",
"view_tag": "66"
}
}
}
],
"extra": [ 1, 16, 197, 117, 248, 72, 72, 198, 97, 239, 230, 252, 60, 13, 106, 170, 134, 73, 34, 19, 245, 80, 117, 12, 20, 175, 246, 162, 224, 112, 189, 60, 30, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}